Skip to content

Commit

Permalink
doc: clarify who may land on an LTS staging branch
Browse files Browse the repository at this point in the history
Current language is a bit confusing

PR-URL: #24465
Refs: #24344 (comment)
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
  • Loading branch information
MylesBorins authored and danbev committed Nov 22, 2018
1 parent c5b326a commit e9545e6
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions COLLABORATOR_GUIDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -803,9 +803,8 @@ pulled from the staging branch into the LTS branch only when a release is
being prepared and may be pulled into the LTS branch in a different order
than they were landed in staging.

Any Collaborator may land commits into a staging branch, but only the release
team should land commits into the LTS branch while preparing a new
LTS release.
Only the members of the @nodejs/backporters team should land commits onto
LTS staging branches.

#### How can I help?

Expand Down

0 comments on commit e9545e6

Please sign in to comment.