Commit d2c8acd
doc: use promote wording in release guide
Signed-off-by: Muhtasim-Munif-Fahim <s1911024120@ru.ac.bd>
PR-URL: #64371
Fixes: #64360
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Stewart X Addison <sxa@redhat.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>1 parent 5c692cb commit d2c8acd
1 file changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -40,7 +40,7 @@ official release builds for Node.js, hosted on <https://nodejs.org/>. | |||
| 40 | 40 | ## Who can make a release? | |
| 41 | 41 | ||
| 42 | 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 | ||
| 43 | + adding the commits to the branches in GitHub and those who can "promote" the | ||
| 44 | 44 | releases to nodejs.org. | |
| 45 | 45 | ||
| 46 | 46 | Individuals who are Members of the | |
@@ -49,12 +49,12 @@ Individuals who are Members of the | |||
| 49 | 49 | releases including creating the proposal branches which will be discussed | |
| 50 | 50 | later in this document. | |
| 51 | 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 | ||
| 52 | + Authorization to promote releases is given by the Node.js TSC. This is | ||
| 53 | + required to promote a release after it has been prepared. If you are working | ||
| 54 | 54 | on preparing a release for the first time you will be able to do most of the | |
| 55 | 55 | steps as a member of the backporters team and have someone else who is | |
| 56 | 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 publish | ||
| 57 | + TSC as a releaser, an individual will require the following to promote | ||
| 58 | 58 | releases themselves: | |
| 59 | 59 | ||
| 60 | 60 | ### 1. Jenkins release access | |
0 commit comments