diff options
| author | Tom Rini <[email protected]> | 2024-04-22 10:44:54 -0600 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2024-04-22 11:01:37 -0600 |
| commit | 9fa8ba1ee1b6ea5361fded5422b19a9b3c1c2ad4 (patch) | |
| tree | d51cd8920da2a52a8308ed4f3c9717b2cc1b7465 /doc/develop/release_cycle.rst | |
| parent | c18ead4ba7b7acd19468264afe06d73255be1bee (diff) | |
doc: release_cycle: Note when next branch opens
While I have said this in various release emails, it should be
documented here as well that the next branch opens with the second
release candidate.
Signed-off-by: Tom Rini <[email protected]>
Diffstat (limited to 'doc/develop/release_cycle.rst')
| -rw-r--r-- | doc/develop/release_cycle.rst | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/develop/release_cycle.rst b/doc/develop/release_cycle.rst index 8d4c112f149..7931521ad9b 100644 --- a/doc/develop/release_cycle.rst +++ b/doc/develop/release_cycle.rst @@ -19,6 +19,9 @@ Cycle as follows: * After the merge window closes, no new features may be added to allow for a release candidate phase which is intended to fix bugs and regressions. +* To help with late pull requests, the **next** branch will open when the + second release candidate is published. + *Note:* While we try to adhere to the release schedule, we will not hesitate and take the liberty to delay a release if there are good reasons, for example if there are known bugs or other technical |