openstack/releases
Code Issues Proposed changes

Merge "Move the "Adding a deliverable" section"

Browse Source
This commit is contained in:
Zuul 2020-06-19 16:06:04 +00:00 committed by Gerrit Code Review
commit c239b4c4fb
2 changed files with 8 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/reference/release_models.rst
View File

@ -147,18 +147,6 @@ two options: develop the new feature in a new library depending on the
stable one, or grant an exception and switch it back to the
`cycle-with-intermediary`_ model.
Adding Deliverables
===================
In order to be considered to be included in the release for a given
series, the project must be documented by adding a deliverable file to
this repository before the second milestone of the series.
Projects created or added to governance after the second milestone
should be released using the independent release model, and then
changed to one of the cycle-based models at the start of the next
cycle.
Legacy release models
=====================

8
doc/source/reference/using.rst
View File

@ -28,6 +28,14 @@ detail below. All automated manipulation of the deliverable is managed
through the data file, which is reviewed by the core team when the
patch is proposed to openstack/releases.
Adding Deliverables
===================
In order to be considered to be included in the release for a given
series, the project must be documented by adding a deliverable file to
this repository before the second milestone of the series. Exceptions
will be considered by the release team on a case-by-case basis.
Requesting a Release
====================