Skip to content

Commit ccffd3b

Browse files
RafaelGSSaduh95
authored andcommitted
doc: enforce strict policy to semver-major releases
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #55732 Refs: nodejs/Release#1054 Reviewed-By: Paolo Insogna <paolo@cowtech.it> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com>
1 parent 9d9ad81 commit ccffd3b

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

doc/contributing/releases.md

+8-2
Original file line numberDiff line numberDiff line change
@@ -1217,8 +1217,14 @@ the releaser, these must be kept in sync with `main`.
12171217
The `vN.x` and `vN.x-staging` branches must be kept in sync with one another
12181218
up until the date of the release.
12191219

1220-
The TSC should be informed of any `SEMVER-MAJOR` commits that land within one
1221-
month of the release.
1220+
If a `SEMVER-MAJOR` pull request lands on the default branch within one month
1221+
prior to the major release date, it must not be included on the new major
1222+
staging branch, unless there is consensus from the Node.js releasers team to
1223+
do so. This measure aims to ensure better stability for the release candidate
1224+
(RC) phase, which begins approximately two weeks prior to the official release.
1225+
By restricting `SEMVER-MAJOR` commits in this period, we provide more time for
1226+
thorough testing and reduce the potential for major breakages, especially in
1227+
LTS lines.
12221228

12231229
### Create release labels
12241230

0 commit comments

Comments
 (0)