openstack/kolla
Code Issues Proposed changes

Add documentation to create monthly stable releases

Browse Source 
Add a reference on how the release tooling can be used.
Add a bullet point to the meeting agenda.
Drop reference to milestones on launchpad, which are no longer being
used.

Change-Id: I66492a7c74a05849b35a157f7782a6596887427f
This commit is contained in:
Dr. Jens Harbott 2022-06-01 14:19:45 +02:00
parent d424a63d60
commit 53880a83cb
2 changed files with 14 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/contributor/meeting.rst
View File

@ -23,6 +23,7 @@ The regular agenda for the weekly meeting is as follows::
* Review action items from the last meeting
* CI status
* Release tasks
* Regular stable releases (first meeting in a month)
* Current cycle planning
* Additional agenda (from whiteboard)
* Open discussion

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

@ -445,15 +445,23 @@ than once every 45 days.
* Create stable releases by submitting patches to the releases repository
* follow SemVer guidelines
* follow SemVer guidelines, for simplicity consider always making minor
version bumps
* example (kolla): https://review.opendev.org/650411
* you can use the tooling from the requirements team to prepare the patches::
* example (kolla-ansible): https://review.opendev.org/650412
git checkout -b kolla-stable-monthly
for project in kayobe kolla kolla-ansible; do
for rel in wallaby xena yoga; do
tox -e venv -- new-release $rel $project feature
done
done
git commit -am "Tag monthly kolla stable releases"
git review -f
* Mark milestones on Launchpad as released
* example release patch (kolla): https://review.opendev.org/650411
* Create new milestones on Launchpad for the next stable releases
* example release patch (kolla-ansible): https://review.opendev.org/650412
Extended Maintenance (EM)
-------------------------