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
---
doc/develop/release_cycle.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/develop/release_cycle.rst b/doc/develop/release_cycle.rst
index 8d4c112f1493..7931521ad9bb 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
--
2.34.1
