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. 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)

^{There may be test issues if the branch used to test does not match the Node.js binary.}

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.

On release proposal branch, edit `src/node_version.h` again and: