Commit 4165cf3
doc: add note about major release rotation
Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
PR-URL: #46436
Fixes: nodejs/Release#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>1 parent f006b2f commit 4165cf3
1 file changed
Lines changed: 4 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1132,6 +1132,10 @@ Major releases should be targeted for the third Tuesday of the release month. | |||
| 1132 | 1132 | A major release must not slip beyond the release month. In other words, major | |
| 1133 | 1133 | releases must not slip into May or November. | |
| 1134 | 1134 | ||
| 1135 | + The @nodejs/releasers make a call for releasers 3 months in advance. | ||
| 1136 | + Currently, this call is automated in the `#nodejs-release-private` | ||
| 1137 | + Slack channel. | ||
| 1138 | + | ||
| 1135 | 1139 | The release date for the next major release should be announced immediately | |
| 1136 | 1140 | following the current release (e.g. the release date for 13.0.0 should be | |
| 1137 | 1141 | announced immediately following the release of 12.0.0). | |
0 commit comments