Skip to content

Commit 7911b9b

Browse files
refackevanlucas
authored andcommitted
doc: examples for fast-tracking regression fixes
PR-URL: #17379 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
1 parent f693e81 commit 7911b9b

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

COLLABORATOR_GUIDE.md

+8-6
Original file line numberDiff line numberDiff line change
@@ -127,12 +127,14 @@ Before landing pull requests, sufficient time should be left for input
127127
from other Collaborators. In general, leave at least 48 hours during the
128128
week and 72 hours over weekends to account for international time
129129
differences and work schedules. However, certain types of pull requests
130-
can be fast-tracked and may be landed after a shorter delay:
131-
132-
* Focused changes that affect only documentation and/or the test suite.
133-
`code-and-learn` and `good-first-issue` pull requests typically fall
134-
into this category.
135-
* Changes that fix regressions.
130+
can be fast-tracked and may be landed after a shorter delay. For example:
131+
132+
* Focused changes that affect only documentation and/or the test suite:
133+
* `code-and-learn` tasks typically fall into this category.
134+
* `good-first-issue` pull requests may also be suitable.
135+
* Changes that fix regressions:
136+
* Regressions that break the workflow (red CI or broken compilation).
137+
* Regressions that happen right before a release, or reported soon after.
136138

137139
When a pull request is deemed suitable to be fast-tracked, label it with
138140
`fast-track`. The pull request can be landed once 2 or more Collaborators

0 commit comments

Comments
 (0)