Skip to content

Commit cd881e3

Browse files
committed
doc: be explicit about who can land on staging
Refs: nodejs/node#24465
1 parent 19985fe commit cd881e3

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,8 @@ Every LTS major version has two branches in the GitHub repository: a release
129129
branch and a staging branch. The release branch is used to cut new releases.
130130
Only members of the release team should land commits into the release branch.
131131
The staging branch is used to land cherry-picked or backported commits from
132-
master that need to be included in a future release.
132+
master that need to be included in a future release. Only members of
133+
@nodejs/backporters should land commits into the staging branch.
133134

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

0 commit comments

Comments
 (0)