openstack/kolla
Code Issues Proposed changes

Update stable release generation doc

Browse Source 
Wallaby has been moved to EM state, so it will receive no more releases.
Also, being optimistic, zed is already being added to the list of stable
branches, so we don't forget it when we actually cut that branch.

Add a small note about this being referenced once per month in regular
Kolla meetings. Also update the example link to a patch that actually
matches the description.

Change-Id: Ie3b4e4461dbfe35808250a929b3e95f880242aed
This commit is contained in:
Dr. Jens Harbott 2022-11-04 11:25:34 +01:00
parent e275875c25
commit 83c1879877
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/contributor/release-management.rst
View File

@ -454,7 +454,8 @@ Maintained
----------
Releases should be made periodically for each maintained stable branch, no less
than once every 45 days.
than once every 45 days. We try to make one release per month by having
a recurring topic for that in the first Kolla meeting each month.
* Create stable releases by submitting patches to the releases repository
@ -465,16 +466,17 @@ than once every 45 days.
git checkout -b kolla-stable-monthly
for project in kayobe kolla kolla-ansible; do
for rel in wallaby xena yoga; do
for rel in xena yoga zed; do
tox -e venv -- new-release $rel $project feature
done
done
for rel in yoga zed; do
tox -e venv -- new-release $rel ansible-collection-kolla feature
done
git commit -am "Tag monthly kolla stable releases"
git review -f
* example release patch (kolla): https://review.opendev.org/650411
* example release patch (kolla-ansible): https://review.opendev.org/650412
* example release patch: https://review.opendev.org/c/openstack/releases/+/860521
Extended Maintenance (EM)
-------------------------