From 7a2090c14ca27d1d94482e91423c4dd8f244f570 Mon Sep 17 00:00:00 2001 From: Rafael Gonzaga Date: Fri, 24 Mar 2023 12:11:18 -0300 Subject: [PATCH] doc: drop one-week branch sync on major releases MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR-URL: https://github.com/nodejs/node/pull/47149 Reviewed-By: Michaël Zasso Reviewed-By: Matteo Collina Reviewed-By: Luigi Pinca Reviewed-By: Colin Ihrig Reviewed-By: Ruy Adorno Reviewed-By: Richard Lau --- doc/contributing/releases.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md index e7fb0f5d0d8b22..9c2d54ba1b4137 100644 --- a/doc/contributing/releases.md +++ b/doc/contributing/releases.md @@ -1148,8 +1148,8 @@ announced immediately following the release of 12.0.0). Approximately two months before a major release, new `vN.x` and `vN.x-staging` branches (where `N` indicates the major release) should be -created as forks of the `main` branch. Up until one week before the release -date, these must be kept in sync with `main`. +created as forks of the `main` branch. Up until the cut-off date announced by +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.