Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: be explicit about who can land on staging #387

Merged
merged 3 commits into from
Nov 19, 2018
Merged

doc: be explicit about who can land on staging #387

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cd881e3
doc: be explicit about who can land on staging
MylesBorins Nov 18, 2018
819ab36
nit: fixup explicit language
richardlau Nov 18, 2018
7d7181e
fixup: minor tweaks
MylesBorins Nov 19, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,9 +127,10 @@ subsequent even-numbered major release is cut.

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.
Only members of the @nodejs/releasers team should land commits onto release branches.
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 onto staging branches.

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