Skip to content

Commit d143c8a

Browse files
committed
doc: make release prepare vs publish distinction clearer
Signed-off-by: Stewart X Addison <sxa@ibm.com>
1 parent 1739f9f commit d143c8a

1 file changed

Lines changed: 17 additions & 13 deletions

File tree

doc/contributing/releases.md

Lines changed: 17 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -39,19 +39,23 @@ official release builds for Node.js, hosted on <https://nodejs.org/>.
3939

4040
## Who can make a release?
4141

42+
There is a distinction between individuals who can "prepare" a release by
43+
adding the commits to the branches in github and those who can "publish" the
44+
releases to nodejs.org.
45+
4246
Individuals who are Members of the
43-
[backporters team](https://github.com/orgs/nodejs/teams/backporters) can
44-
land things on the staging branches and prepare releases. This is a
45-
prerequisite to being able to prepare a release which is the first step
46-
to becoming a releaser.
47-
48-
Release authorization is given by the Node.js TSC. This is required to
49-
promote a release after it has been prepared. If you are working on
50-
preparing a release for the first time you can do most of the steps to
51-
prepare the proposal branch as a member of the backporters team and have
52-
someone else who is already onboarded promote the release on your behalf.
53-
Once authorized by the TSC, an individual will require the following to
54-
complete releases themselves:
47+
[backporters team](https://github.com/orgs/nodejs/teams/backporters)
48+
(restricted link) can land things on the staging branches and prepare
49+
releases including creating the proposal branches which will be discussed
50+
later in this document.
51+
52+
Authorization to publish releases is given by the Node.js TSC. This is
53+
required to publish a release after it has been prepared. If you are working
54+
on preparing a release for the first time you will be able to do most of the
55+
steps as a member of the backporters team abd have someone else who is
56+
already onboarded promote the release on your behalf. Once authorized by the
57+
TSC as a releaser, an individual will require the following to complete releases
58+
themselves:
5559

5660
### 1. Jenkins release access
5761

@@ -98,7 +102,7 @@ _dist_ user.
98102

99103
Release builds require manual promotion by an individual with SSH access to the
100104
server as the _dist_ user. The
101-
[Node.js build team](https://github.com/nodejs/build) is able to provide this
105+
[Node.js build team](lhttps://github.com/nodejs/build) is able to provide this
102106
access to individuals authorized by the TSC.
103107

104108
### 3. A publicly-listed GPG key

0 commit comments

Comments
 (0)