openstack/releases
Code Issues Proposed changes
Release requests and history tracking
11,994 Commits 1 Branch 0 Tags 131 MiB
Python 89.7%
Shell 10.3%
cbacc8fe03
Go to file
Chandan kumar cbacc8fe03 Create pike-eol tag for all TripleO projects 
TripleO Team is no longer accepting patches to
stable/pike branch, this patch proposes to create pike-eol
tags for all TripleO projects.

Change-Id: I62acc422bb7e0c61dfb780358bedb551c2d9825f
Signed-off-by: Chandan kumar (raukadah) <chkumar@redhat.com>
2019-08-26 21:13:16 +05:30
data Update placement release liaisons 2019-07-01 14:54:16 +01:00
deliverables Create pike-eol tag for all TripleO projects 2019-08-26 21:13:16 +05:30
doc Merge "cycle-with-intermediary release process details" 2019-08-22 16:39:42 +00:00
openstack_releases Skip minor version increment validation for branchless 2019-08-08 12:19:33 -05:00
templates switch mailing lists to openstack-discuss 2018-12-04 10:41:28 -05:00
tools Fix bashate errors 2019-07-08 11:46:30 -05:00
.gitignore Switch to stestr 2018-07-10 10:38:33 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:37:48 +00:00
.stestr.conf Switch to stestr 2018-07-10 10:38:33 +07:00
.zuul.yaml Add Python 3 Train unit tests 2019-07-19 14:43:41 -04:00
bindep.txt install the python3 version of launchpadlib 2018-06-21 16:28:06 -04:00
CONTRIBUTING.rst Document tag pipeline jobs in contributor doc 2019-06-06 12:10:45 +02:00
LICENSE Add top level LICENSE file 2018-10-17 10:36:04 +11:00
README.rst Point to release-management info in governance 2018-11-01 16:09:48 +01:00
requirements.txt Switch to ruamel for yaml handling 2019-07-08 11:40:11 -05:00
setup.cfg Merge "Add Python 3 Train unit tests" 2019-08-08 09:50:12 +00:00
setup.py [Trivial] Remove executable privilege of setup.py 2016-05-09 16:38:37 +00:00
test-requirements.txt Switch to stestr 2018-07-10 10:38:33 +07:00
tox.ini Merge "Add Python 3 Train unit tests" 2019-08-08 09:50:12 +00:00
watched_queries.yml Rename review.openstack.org to review.opendev.org 2019-05-12 04:33:25 +08:00
yamllint.yml add linter rules for vertical whitespace 2017-07-31 17:26:33 -04:00

README.rst

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.