Skip to content

Conversation

@AThousandShips
Copy link
Member

Currently WIP but adjusting to changing workflows and will add some additional details to the priorities page but opening to start tracking this

@AThousandShips AThousandShips added the enhancement New feature or request label Nov 25, 2025
@AThousandShips AThousandShips changed the title [WIP] Rename release blockers [WIP][Triage] Improve the release priority page Nov 28, 2025
@AThousandShips
Copy link
Member Author

Added a number of details from the internal workflow, still a work in progress but contains most of the information I believe belongs and mostly needs to be cleaned up for wording

Copy link

@Cykyrios Cykyrios left a comment

Choose a reason for hiding this comment

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

Typos/phrasing suggestions, otherwise looks good to me, and it certainly makes more sense not to call all those issues "blockers".

@AThousandShips
Copy link
Member Author

Thank you! Applied


The following is a checklist to determine if an issue is a release priority or not.

If an issue is old (over 6 months), and hasn't gotten worse, or gotten new duplicate issues
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't this part go in the "is it a regression" part?

Copy link
Member Author

Choose a reason for hiding this comment

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

No it's not related to regressions, it's a general suggestion (was a heading of its own originally but works better here)

@AThousandShips AThousandShips force-pushed the blockers branch 2 times, most recently from 4c933d6 to 226895f Compare December 1, 2025 13:09
Renamed from release blockers and adding more workflow details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants