Skip to content

doc: use promote wording in release guide #64371

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

Open
Muhtasim-Munif-Fahim wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −4
Open

doc: use promote wording in release guide #64371

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions doc/contributing/releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ official release builds for Node.js, hosted on <https://nodejs.org/>.
## Who can make a release?

There is a distinction between individuals who can "prepare" a release by
adding the commits to the branches in GitHub and those who can "publish" the
adding the commits to the branches in GitHub and those who can "promote" the
releases to nodejs.org.

Individuals who are Members of the
Expand All @@ -49,12 +49,12 @@ Individuals who are Members of the
releases including creating the proposal branches which will be discussed
later in this document.

Authorization to publish releases is given by the Node.js TSC. This is
required to publish a release after it has been prepared. If you are working
Authorization to promote releases is given by the Node.js TSC. This is
required to promote a release after it has been prepared. If you are working
on preparing a release for the first time you will be able to do most of the
steps as a member of the backporters team and have someone else who is
already onboarded promote the release on your behalf. Once authorized by the
TSC as a releaser, an individual will require the following to publish
TSC as a releaser, an individual will require the following to promote
releases themselves:

### 1. Jenkins release access
Expand Down
Loading