Skip to content

docs(Documentation): Updated sprint guide #741

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bari12 wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −1
Open

docs(Documentation): Updated sprint guide #741

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/developer/sprint_planning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ This is indicated by the presence of a `priority` label on the issue.

Sub-issues of `priority` issues should also be labeled as `priority`.
This is because a `priority` issue might be too large (see the [Size estimation](#size-estimation) section) to fit in a single sprint,
and it should be broken down into sub-issues, which should still be prioritised over non-priority issues.
and it should/must be broken down into sub-issues, which should still be prioritised over non-priority issues.
Copy link
Contributor

@voetberg voetberg Feb 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It probably should just be "must" - this isn't really optional

Copy link
Contributor

@rdimaio rdimaio Feb 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO it should be either should or must, "should/must" doesn't really convey whether this is optional or not



### Size estimation
Expand All @@ -54,6 +54,8 @@ The following labels are available for size estimation:
- **L**: about one week (5 days) of work. This issue **should** be broken down into individual sub-issues
- **XL**: more than one week (5 days) of work. This issue **must** be broken down into individual sub-issues

For **LARGE** and **XLARGE** issues it is mandatory to select/nominate a reviewer/co-author at the time of creation of the issue. This is to ensure
Copy link
Contributor

@voetberg voetberg Feb 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this apply to the collection type L/XL issues? (e.g - #363 rucio/rucio#7658 )

that the approach and planned work is discussed already before the implementation is started.

## Moderating a sprint
Each sprint is moderated by one of the developers. This role rotates on a voluntary basis.
Expand Down