-
-
Notifications
You must be signed in to change notification settings - Fork 11
[WIP][Triage] Improve the release priority page #33
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.
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
base: main
Are you sure you want to change the base?
Conversation
7b22f0c to
92f9d6f
Compare
|
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 |
Cykyrios
left a comment
There was a problem hiding this 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".
92f9d6f to
ae05e32
Compare
|
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 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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)
4c933d6 to
226895f
Compare
Renamed from release blockers and adding more workflow details
Currently WIP but adjusting to changing workflows and will add some additional details to the priorities page but opening to start tracking this