doc: add note about major release rotation

Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
PR-URL: https://github.com/nodejs/node/pull/46436
Fixes: https://github.com/nodejs/Release/issues/765
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
Reviewed-By: Ruy Adorno <ruyadorno@google.com>
pull/46473/head
Rafael Gonzaga 2023-02-02 09:39:18 -03:00 committed by GitHub
parent 61c65b066b
commit 60996372c4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions

View File

@ -1132,6 +1132,10 @@ Major releases should be targeted for the third Tuesday of the release month.
A major release must not slip beyond the release month. In other words, major
releases must not slip into May or November.
The @nodejs/releasers make a call for releasers 3 months in advance.
Currently, this call is automated in the `#nodejs-release-private`
Slack channel.
The release date for the next major release should be announced immediately
following the current release (e.g. the release date for 13.0.0 should be
announced immediately following the release of 12.0.0).