QA/releases
< QA
Revision as of 22:16, 20 April 2020 by Ghanshyam Mann (talk | contribs) (Update the release process for all the QA projects with example and steps.)
OpenStack QA releases its tooling as per each tool release model and also needs to take care of the new branch set on devstack and grenade. This page explain the process and tasks QA team needs to do on every OpenStack release.
Contents
Project Releases
Project with release mode: cycle-with-intermediary
Tempest
- Step1: Add Release note to mark the release
- Example:
- Intermediate release https://review.openstack.org/#/c/514873/2
- Cycle release –https://review.opendev.org/#/c/685401/
- EOL stable release – https://review.opendev.org/#/c/703255/
- Example:
- Step2: Push release tag to openstack/release repo
- Example:
- Intermediate - https://review.opendev.org/#/c/688613/
- Cycle release- https://review.opendev.org/#/c/685406/
- Example:
- Step3: Add release notes page after release patch is merged
- Example:
- Cycle Release- https://review.opendev.org/#/c/687123/
- Example:
- Step4: Add releasenotes page link in openstck/release
- Step5: Remove the End of Support branch job from tempest gate if release is for end of support for any stable branch
Patrole
- Step1: Add Release note to mark the release
- Step2: Push release tag to openstack/release repo
- Step3: Add release notes page after release patch is merged
- Step4: Add releasenotes page link in openstck/release
- Step5: Remove the End of Support branch job from tempest gate if release is for end of support for any stable branch:
Project with release mode: independent
Below projects are with independent release and not associated with OpenStack cycle release.
- hacking
- os-testr
- bashate
- devstack-tools
- eslint-config-openstack
Project with no release
Below projects are with no release and maintained as master version only.
- coverage2sql
- devstack-plugin-ceph
- devstack-plugin-cookiecutter
- devstack-plugin-open-cas
- devstack-plugin-nfs
- devstack-vagrant
- karma-subunit-reporter
- openstack-health
- os-performance-tools
- stackviz
- tempest-stress
- tempest-plugin-cookiecutter
Projects with only Branches
For the most part, Devstack and Grenade only have branches, which need to be cut when other projects get stable/* branches during a release.
- Devstack
- Step1: Wait for stable/* branch to exist on the projects in Devstack repo
- Step2: Propose to openstack/releases to create a stable/foo branch for Devstack
- Step3: Update .gitreview for stable/foo – patch from OpenStack Release Bot
- Step4: Update branches for stable/foo
- Step5: Update DEVSTACK_SERIES on master Devstack
- Step6: Update lib/tempest to hardcode max microversions and extensions on stable/foo
- Step7: After Devstack has been branched. Add a new stable branch job in the Tempest pipeline.
- Step8: After Devstack has been branched. Configure devstack-gate to run the new stable branch jobs.
- Step9: After Devstack has been branched. Add the new stable branch to the list of branches in the periodic-stable job templates in openstack-zuul-jobs.
- Grenade
- Step1: Wait for stable/branch to exist on Devstack
- Step2: Propose to openstack/releases to create a stable/foo branch
- Step3: Update .gitreview for stable/x – from OpenStack Release Bot
- Step5: Update devstack-gate logic to use the new branches
- Example: new- https://review.openstack.org/#/c/591594/
- devstack-plugin-container: hanled by devstack-plugin-container team.
Once all done then you deserve to go for beer \o/
