Skip to content

docs(Documentation): Updated sprint guide#741

Open
bari12 wants to merge 1 commit intorucio:mainfrom
bari12:sprint_doc
Open

docs(Documentation): Updated sprint guide#741
bari12 wants to merge 1 commit intorucio:mainfrom
bari12:sprint_doc

Conversation

@bari12
Copy link
Member

@bari12 bari12 commented Feb 4, 2026

No description provided.

@bari12 bari12 requested a review from voetberg February 5, 2026 16:30
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

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

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

- **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

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 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants