Skip to content

Commit

Permalink
doc: specify fast-tracking
Browse files Browse the repository at this point in the history
Currently the documentation is not specific how fast-tracking should
be applied. This specifies exactly how things should be done to prevent
confusion.
  • Loading branch information
BridgeAR committed Sep 18, 2018
1 parent ba0b4e4 commit c0c5247
Showing 1 changed file with 6 additions and 3 deletions.
9 changes: 6 additions & 3 deletions COLLABORATOR_GUIDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,9 +183,12 @@ can be fast-tracked and may be landed after a shorter delay. For example:
* Regressions that happen right before a release, or reported soon after.

When a pull request is deemed suitable to be fast-tracked, label it with
`fast-track`. The pull request can be landed once 2 or more Collaborators
approve both the pull request and the fast-tracking request, and the necessary
CI testing is done.
`fast-track` and add a comment that collaborators may upvote. Please mention the
collaborators that gave an approval before in that comment. If someone disagrees
with the fast-tracking request, please go ahead and remove the label and leave a
comment why it should not be fast-tracked. The pull request can be landed once 2
or more Collaborators approve both the pull request and the fast-tracking
request, and the necessary CI testing is done.

### Testing and CI

Expand Down

0 comments on commit c0c5247

Please sign in to comment.