@@ -81,6 +81,23 @@ Notes:
8181- Version strings are listed below as _ "vx.y.z"_ . Substitute for the release
8282 version.
8383
84+ ### 0. Pre-release steps
85+
86+ Before preparing a Node.js release, the Build Working Group must be notified at
87+ least one business day in advance of the expected release. Coordinating with
88+ Build is essential to make sure that the CI works, release files are published,
89+ and the release blog post is available on the project website.
90+
91+ Build can be contacted best by opening up an issue on the [ Build issue tracker] [ ] ,
92+ and by posting in ` #node-build ` on [ webchat.freenode.net] [ ] .
93+
94+ When preparing a security release, contact Build at least two weekdays in
95+ advance of the expected release. To ensure that the security patch(es) can be
96+ properly tested, run a ` node-test-pull-request ` job against the ` master ` branch
97+ of the ` nodejs-private/node-private ` repository a day or so before the
98+ [ CI lockdown procedure] [ ] begins. This is to confirm that Jenkins can properly
99+ access the private repository.
100+
84101### 1. Cherry-picking from ` master ` and other branches
85102
86103Create a new branch named _ "vx.y.z-proposal"_ , or something similar. Using `git
@@ -517,4 +534,7 @@ Close your release proposal PR and remove the proposal branch.
517534
518535_ In whatever form you do this..._
519536
537+ [ CI lockdown procedure ] : https://github.com/nodejs/build/blob/master/doc/jenkins-guide.md#restricting-access-for-security-releases
538+ [ Build issue tracker ] : https://github.com/nodejs/build/issues/new
520539[ nodejs.org release-post.js script ] : https://github.com/nodejs/nodejs.org/blob/master/scripts/release-post.js
540+ [ webchat.freenode.net ] : https://webchat.freenode.net/
0 commit comments