-
Notifications
You must be signed in to change notification settings - Fork 30k
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
doc: examples for fast-tracking regression fixes #17379
doc: examples for fast-tracking regression fixes #17379
Conversation
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.
Thanks
|
||
* Focused changes that affect only documentation and/or the test suite: | ||
* `code-and-learn` tasks typically fall into this category. | ||
* `good-first-issue` pull requests may also be suitable. |
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.
How about:
Pull requests from new contributors (for example
code-and-learn
tasks) that are low-risk and uncontentious.
- If the aim is to improve the experience of your first node contribution, then let's say that specifically.
- If we say docs or tests only, does that cover source comments? Or whitespace fixes? I feel like specifying the "what" is going to be too complex, but the "why" might be easier.
* `good-first-issue` pull requests may also be suitable. | ||
* Changes that fix regressions: | ||
* Regressions that break the workflow (red CI or broken compilation). | ||
* Regressions that happen right before a release, or reported soon after. |
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.
Maybe: "Fixes that need to be backported to a release line urgently."
If it's reported soon after a release and we decided to leave it till the next one, then it doesn't need to be fast-tracked IMO.
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.
I think this is just listing changes that "can be" fast-tracked, not necessarily "need to be"?
PR-URL: #17379 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Landed in 4c8bedf |
PR-URL: #17379 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
PR-URL: #17379 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
PR-URL: #17379 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
PR-URL: #17379 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Follow up to #17332
Checklist
Affected core subsystem(s)
dec,meta