openstack/releases
Code Issues Proposed changes

document policy on adding new deliverables

Browse Source 
Change-Id: I639eecf05e0dcd6bee5e4390c80ce491a8fefc39
Story: 2001845
Task: 12613
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2018-11-06 11:35:01 -05:00
parent af8f7604b5
commit 9f88d58f33
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -169,3 +169,15 @@ a library were to need large feature development work again, we'd have
two options: develop the new feature in a new library depending on the 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 stable one, or grant an exception and switch it back to the
`cycle-with-intermediary`_ model. `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.