From 5767b76c301fef24bc42eaafb3f6fd066783946e Mon Sep 17 00:00:00 2001 From: Rafael Gonzaga Date: Thu, 7 Nov 2024 16:08:56 -0300 Subject: [PATCH] doc: enforce strict policy to semver-major releases MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Antoine du Hamel PR-URL: https://github.com/nodejs/node/pull/55732 Refs: https://github.com/nodejs/Release/issues/1054 Reviewed-By: Paolo Insogna Reviewed-By: Matteo Collina Reviewed-By: Michaël Zasso Reviewed-By: Ulises Gascón Reviewed-By: Antoine du Hamel Reviewed-By: Marco Ippolito Reviewed-By: Richard Lau --- doc/contributing/releases.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md index 0160d94fea5a61..400aa51fb2667d 100644 --- a/doc/contributing/releases.md +++ b/doc/contributing/releases.md @@ -1217,8 +1217,14 @@ the releaser, these must be kept in sync with `main`. The `vN.x` and `vN.x-staging` branches must be kept in sync with one another up until the date of the release. -The TSC should be informed of any `SEMVER-MAJOR` commits that land within one -month of the release. +If a `SEMVER-MAJOR` pull request lands on the default branch within one month +prior to the major release date, it must not be included on the new major +staging branch, unless there is consensus from the Node.js releasers team to +do so. This measure aims to ensure better stability for the release candidate +(RC) phase, which begins approximately two weeks prior to the official release. +By restricting `SEMVER-MAJOR` commits in this period, we provide more time for +thorough testing and reduce the potential for major breakages, especially in +LTS lines. ### Create release labels