yatinkarel
d6820ceb0a
Last tag was created more than 2 years ago since then master have included couple of features and bug fixes. It would be good to get a tag release for current master and also a stable/2.0 to backport fixes into it. Add stable-branch-type: upstream to allow naming scheme apart from openstack release names. Also add seperate release type for openstack-virtual-baremetal as it's not publishing other pypi or tarball artifacts. Change-Id: Ia8c9c5e8ad577f6ec1796591e77fddaffa62f008
OpenStack Releases
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.
For more information on how to use this repository, please read our reference documentation.
Who should use this repository
All official OpenStack software should go through the OpenStack Release Management team team to produce releases. Exceptions to this rule are granted by the Technical Committee and documented in the openstack/governance repository ('release-management' key in reference/projects.yaml).
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.
More information
You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.