Sean McGinnis
0c265869aa
Cycle trailing deliverables are often not released by the time we initialize the next series. We add a comment to deliverable files during their creation to note if they were not released in the last cycle to help highlight orphaned deliverables. This can be misleading for cycle trailing deliverables, since usually they do end up being released, but after we've created the file and included the comment. To make this comment more useful, this removes its inclusion for trailing projects. Change-Id: I010dadc2ca9026248e7f9dfc89d257afdf97be72 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
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.