aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Rini <trini@konsulko.com>2024-04-22 10:44:54 -0600
committerTom Rini <trini@konsulko.com>2024-04-22 11:01:37 -0600
commit9fa8ba1ee1b6ea5361fded5422b19a9b3c1c2ad4 (patch)
treed51cd8920da2a52a8308ed4f3c9717b2cc1b7465
parentc18ead4ba7b7acd19468264afe06d73255be1bee (diff)
downloadu-boot-9fa8ba1ee1b6ea5361fded5422b19a9b3c1c2ad4.zip
u-boot-9fa8ba1ee1b6ea5361fded5422b19a9b3c1c2ad4.tar.gz
u-boot-9fa8ba1ee1b6ea5361fded5422b19a9b3c1c2ad4.tar.bz2
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 <trini@konsulko.com>
-rw-r--r--doc/develop/release_cycle.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/develop/release_cycle.rst b/doc/develop/release_cycle.rst
index 8d4c112..7931521 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