nodejs
/
node
mirror of https://github.com/nodejs/node.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: clarify release process for new releasers 

PR-URL: https://github.com/nodejs/node/pull/43739
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
This commit is contained in:
Rafael Gonzaga 2022-07-13 14:30:19 -03:00 committed by GitHub
parent a8f6c563e6
commit 2f169ad58a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/contributing/releases.md
View File

@ -468,7 +468,20 @@ failed build if you start again!
Jenkins collects the artifacts from the builds, allowing you to download and
install the new build. Make sure that the build appears correct. Check the
version numbers, and perform some basic checks to confirm that all is well with
the build before moving forward.
the build before moving forward. Use the following list as a baseline:
* `process.version` is as expected
* `process.release` is as expected
* `process.versions` is as expected (for example, `openssl` or `llhttp` version
must be in the expected updated version)
* npm version (check it matches what we expect)
* Run the test suite against the built binaries (optional)
```console
./tools/test.py --shell ~/Downloads/node-v18.5.0-linux-x64/bin/node
```
<sup>There may be test issues if the branch used to test does not match the Node.js binary.</sup>
### 11. Tag and sign the release commit
@ -510,6 +523,8 @@ include the release code name.
The tag **must** be signed using the GPG key that's listed for you on the
project README.
**Note**: Don't push the tag to remote at this point.
### 12. Set up for the next release
On release proposal branch, edit `src/node_version.h` again and: