Tony Breeds 752ce5a491 Generate the constraints redirections from the deliverable data
Instead of statically listing the redirections move to a dynamic model.

We move the existing _extras/.htaccess to _templates/htaccess so we have
some control and safety of what goes in there.  Connect 'build-finished'
from _exts.deliverables.py to trigger generating the redirects.  Doing
so here avoids re-reading the data as deliverables.py ahas already done
that for us.

Change-Id: If6bd59fd478593a84ebcedc3a50af3720d620d3c
2019-02-28 12:50:37 +11:00
2019-02-27 20:11:29 +00:00
2018-07-10 10:38:33 +07:00
2015-07-02 09:25:52 +00:00
2018-07-10 10:38:33 +07:00
2018-11-05 20:58:02 +01:00
2018-10-17 10:36:04 +11:00
2018-07-10 10:38:33 +07:00

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.

image

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.

S
Description
Release requests and history tracking
Readme Apache-2.0
148 MiB
Languages
Python 88.8%
Shell 11.2%