Skip to content

Commit ab6588e

Browse files
RafaelGSSdanielleadams
authored andcommittedJul 6, 2023
doc: drop one-week branch sync on major releases
PR-URL: #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>
1 parent 6ac52e3 commit ab6588e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed
 

‎doc/contributing/releases.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1148,8 +1148,8 @@ announced immediately following the release of 12.0.0).
11481148

11491149
Approximately two months before a major release, new `vN.x` and
11501150
`vN.x-staging` branches (where `N` indicates the major release) should be
1151-
created as forks of the `main` branch. Up until one week before the release
1152-
date, these must be kept in sync with `main`.
1151+
created as forks of the `main` branch. Up until the cut-off date announced by
1152+
the releaser, these must be kept in sync with `main`.
11531153

11541154
The `vN.x` and `vN.x-staging` branches must be kept in sync with one another
11551155
up until the date of the release.

0 commit comments

Comments
 (0)
Please sign in to comment.