Skip to content

Commit

Permalink
doc: be explicit about who can land on staging
Browse files Browse the repository at this point in the history
  • Loading branch information
MylesBorins committed Nov 18, 2018
1 parent 19985fe commit cd881e3
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,8 @@ Every LTS major version has two branches in the GitHub repository: a release
branch and a staging branch. The release branch is used to cut new releases.
Only members of the release team should land commits into the release branch.
The staging branch is used to land cherry-picked or backported commits from
master that need to be included in a future release.
master that need to be included in a future release. Only members of
@nodejs/backporters should land commits into the staging branch.

For example, for Node.js v4, there is a `v4.x` branch and a `v4.x-staging`
branch. When commits land in master that must be cherry-picked for a future
Expand Down

0 comments on commit cd881e3

Please sign in to comment.