doc: drop one-week branch sync on major releases

PR-URL: #47149 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Richard Lau <[email protected]>
nodejs · Jul 6, 2023 · ab6588e · ab6588e
1 parent 6ac52e3
commit ab6588e
Showing 1 changed file with 2 additions and 2 deletions.
diff --git 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.