Release requests and history tracking
727d9c37df
Sometimes creating the branches immediately for projects can comes as a surprise and cause a little extra work with backports when they have critical fixes to include with a requirements FFE. To avoid some of this, change the branch creation policy to allow it at freeze time but do not enforce it as a requirement. Then create the branches for any missed deliverables closer to the end of the cycle. Change-Id: Ib6f4037c450a00080a5e9a2a7665c6ea4d112ba5 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com> |
||
---|---|---|
deliverables | ||
doc | ||
openstack_releases | ||
templates | ||
tools | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
watched_queries.yml | ||
yamllint.yml |
Using This Repository
This repository is for tracking release requests for OpenStack projects. The 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.
The repository is managed by the Release Management team.
Refer to the reference documentation for more details