a68f6bede5
The list-changes job would fail to parse deliverable files with the error "WARNING: Unable to parse $repo $series deliverable file" due to the repo name being passed in with the leading openstack/ namespace. This is common code used by list-changes and release-notes. In list-changes we have the actual name of the deliverable file, so just use that if it is available. Also makes sure that cases were we expect just the repo name without namespace only get what is expected. Change-Id: Ib7526fc66d05530c2c2c722284c1d64a5242e419 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Using This Repository
All official OpenStack software should go through the 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).
This repository is used to track release requests. Releases are managed using groups of "deliverables", made up of individual project repositories sharing a Launchpad group and a version number history. Many deliverables will only have one constituent project repository.
The repository is managed by the Release Management team.
Refer to the reference documentation for more details
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.