mirror of https://github.com/nodejs/node.git
doc: drop one-week branch sync on major releases
PR-URL: https://github.com/nodejs/node/pull/47149 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruy Adorno <ruyadorno@google.com> Reviewed-By: Richard Lau <rlau@redhat.com>pull/47248/head
parent
545b594b19
commit
5e72051456
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue