doc: add note about major release rotation #46436
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Review requested:
|
GeoffreyBooth
reviewed
Jan 31, 2023
| @@ -1126,6 +1126,9 @@ 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 |
There was a problem hiding this comment.
Suggested change
| Currently, this call is automated in the #nodejs-release-private slack channel | |
| Currently, this call is automated in the `#nodejs-release-private` Slack channel. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Fixes: nodejs/Release#765
cc: @nodejs/releasers