Skip to content

doc: clarify who may land on an LTS staging branch #24465

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

Closed
wants to merge 5 commits into from
Closed

doc: clarify who may land on an LTS staging branch #24465

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ca101da
doc: clarify who may land on an LTS staging branch
MylesBorins Nov 18, 2018
ae50ca1
fixup: update text
Trott Nov 18, 2018
6328008
fixup: clarify further
MylesBorins Nov 18, 2018
db735ad
fixup: sigh
MylesBorins Nov 18, 2018
1df57da
fixup: minor tweak from jasnell
MylesBorins Nov 18, 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: 2 additions & 3 deletions COLLABORATOR_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -802,9 +802,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