openstack/releases
Code Issues Proposed changes

Add requirements freeze to mitaka schedule

Browse Source 
Change-Id: If27543e970c07118b37a8e85ab9ca2c9f68edbe1
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2016-02-05 15:07:53 -05:00
parent 79acf7a993
commit a9d2c81eb6
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/source/mitaka/schedule.rst
View File

@ -57,6 +57,8 @@
| | +---------------------------+-----------------------------+
| | | :ref:`m-ff` | |
| | +---------------------------+-----------------------------+
| | | :ref:`m-rf` | |
| | +---------------------------+-----------------------------+
| | | :ref:`m-final-clientlib` | |
| | +---------------------------+-----------------------------+
| | | :ref:`m-soft-sf` | |
@ -128,6 +130,18 @@ The mitaka-3 milestone marks feature freeze for projects following the
release:cycle-with-milestones model. No featureful patch should be landed
after this point. Exceptions may be granted by the project PTL.
.. _m-rf:
Requirements freeze
-------------------
After the mitaka-3 milestone, only critical requirements and
constraints changes will be allowed. Freezing our requirements list
gives packagers downstream an opportunity to catch up and prepare
packages for everything necessary for distributions of the upcoming
release. The requirements remain frozen until the stable branches are
created, with the release candidates.
.. _m-final-clientlib:
Final release for client libraries