openstack
/
project-team-guide
Code Issues Proposed changes

Add section about transition 

The `unmaintained` section does not clearly spell out how the transition
to this new branch structure is to be transitioned for branches before
the first SLURP release.

Change-Id: Ica33e5cfe0e5ba84e1bf648393eb2c7b788be5f1
Signed-off-by: Nicolas Bock <nicolas.bock@canonical.com>
This commit is contained in:
Nicolas Bock 2024-03-05 13:24:22 -07:00
parent 7cc5e309c3
commit 3591921da0
No known key found for this signature in database
GPG Key ID: 04F8F5442B67A58D
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/source/stable-branches.rst
View File

@ -187,6 +187,20 @@ upgrade path from one SLURP to the next all the way to maintained releases.
plugins, take a look at these Gerrit reviews:
https://review.opendev.org/q/topic:%22tempest-plugin-stein-last%22+(status:open%20OR%20status:merged)
Transition
==========
The current Extended Maintenance branches are not SLURP releases and wouldn’t be
eligible for Unmaintained branches with the guidelines above. The first SLURP
release is 2023.1.
- Until the first SLURP release ends its maintained phase, all current branches
are eligible for Unmaintained.
- The last 3 active Extended Maintenance branches are automatically transitioned
to Unmaintained branches.
- The unmaintained branch liaison needs to opt-in to keep more than 3 branches
(instead of 1 for SLURP) and the guidelines for opt-in described above apply.
.. _End Of Life:
End of Life
@ -628,4 +642,3 @@ policy (project stop or start following the stable branch policy).
.. _Sahara: https://governance.openstack.org/tc/reference/projects/sahara.html
.. _Swift: https://governance.openstack.org/tc/reference/projects/swift.html
.. _Zaqar: https://governance.openstack.org/tc/reference/projects/zaqar.html