Proposed release schedule for Rocky
Assuming we will stay with a 6 month release cycle for Rocky, this is a proposed schedule for the Rocky cycle. One thing to note is the date for the S PTG has not been finalized yet, so we may need or want to push out the window between one of the milestones so there is not too long of a gap between Rocky being released and the next PTG being held. Change-Id: I0e26b443b7d4cf64f834b9726342cdfab54d36e7
This commit is contained in:
Sean McGinnis
@@ -21,6 +21,11 @@ updates.
|
|||||||
* Initial Release Date
|
* Initial Release Date
|
||||||
* Next Phase
|
* Next Phase
|
||||||
* EOL Date
|
* EOL Date
|
||||||
|
- * :doc:`rocky/index`
|
||||||
|
* :doc:`Future <rocky/schedule>`
|
||||||
|
* :ref:`proposed <r-release>`
|
||||||
|
*
|
||||||
|
* TBD
|
||||||
- * :doc:`queens/index`
|
- * :doc:`queens/index`
|
||||||
* :doc:`Under Development <queens/schedule>`
|
* :doc:`Under Development <queens/schedule>`
|
||||||
* :ref:`scheduled <q-release>`
|
* :ref:`scheduled <q-release>`
|
||||||
@@ -116,6 +121,7 @@ updates.
|
|||||||
:maxdepth: 1
|
:maxdepth: 1
|
||||||
:hidden:
|
:hidden:
|
||||||
|
|
||||||
|
rocky/index
|
||||||
queens/index
|
queens/index
|
||||||
pike/index
|
pike/index
|
||||||
ocata/index
|
ocata/index
|
||||||
|
|||||||
15
doc/source/rocky/index.rst
Normal file
15
doc/source/rocky/index.rst
Normal file
@@ -0,0 +1,15 @@
|
|||||||
|
=======
|
||||||
|
Rocky
|
||||||
|
=======
|
||||||
|
|
||||||
|
Projected Release Date: 30 August, 2018
|
||||||
|
|
||||||
|
.. toctree::
|
||||||
|
:maxdepth: 1
|
||||||
|
|
||||||
|
|
||||||
|
schedule
|
||||||
|
|
||||||
|
|
||||||
|
.. deliverable::
|
||||||
|
:series: rocky
|
||||||
233
doc/source/rocky/schedule.rst
Normal file
233
doc/source/rocky/schedule.rst
Normal file
@@ -0,0 +1,233 @@
|
|||||||
|
========================
|
||||||
|
Rocky Release Schedule
|
||||||
|
========================
|
||||||
|
|
||||||
|
1 March 2018 - 29 August 2018 (26 weeks)
|
||||||
|
|
||||||
|
.. datatemplate::
|
||||||
|
:source: schedule.yaml
|
||||||
|
:template: schedule_table.tmpl
|
||||||
|
|
||||||
|
.. ics::
|
||||||
|
:source: schedule.yaml
|
||||||
|
:name: Rocky
|
||||||
|
|
||||||
|
`Subscribe to iCalendar file <schedule.ics>`__
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
With the exception of the final release date and cycle-trailing
|
||||||
|
release date, deadlines are generally the Thursday of the week on
|
||||||
|
which they are noted above. For example, the Feature Freeze in week
|
||||||
|
R-5 is on 26 July. Exceptions to this policy will be explicitly
|
||||||
|
mentioned in the event description.
|
||||||
|
|
||||||
|
Cross-project events
|
||||||
|
====================
|
||||||
|
|
||||||
|
.. _r-goals-research:
|
||||||
|
|
||||||
|
Rocky Goals Research
|
||||||
|
--------------------
|
||||||
|
|
||||||
|
Pre-cycle planning and investigation into `the community-wide goals
|
||||||
|
for Rocky <https://governance.openstack.org/tc/goals/rocky/index.html>`__.
|
||||||
|
|
||||||
|
.. _r-ptg:
|
||||||
|
|
||||||
|
Rocky Project Team Gathering (PTG)
|
||||||
|
----------------------------------
|
||||||
|
|
||||||
|
`Project team gathering <https://www.openstack.org/ptg>`__ for the Rocky
|
||||||
|
cycle 26 February - 2 March 2018 in Dublin, Ireland.
|
||||||
|
|
||||||
|
.. _r-1:
|
||||||
|
|
||||||
|
Rocky-1 milestone
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
19 April 2018 is the Rocky-1 milestone window for projects following the
|
||||||
|
`release:cycle-with-milestones`_ model.
|
||||||
|
|
||||||
|
.. _release:cycle-with-milestones: https://releases.openstack.org/reference/release_models.html#cycle-with-milestones
|
||||||
|
|
||||||
|
.. _r-goals-ack:
|
||||||
|
|
||||||
|
Rocky Community Goals Acknowledgement
|
||||||
|
-------------------------------------
|
||||||
|
|
||||||
|
Teams should prepare their acknowledgement of `the community-wide
|
||||||
|
goals for
|
||||||
|
<https://governance.openstack.org/tc/goals/queens/index.html>`__.
|
||||||
|
|
||||||
|
.. _r-summit:
|
||||||
|
|
||||||
|
OpenStack Summit
|
||||||
|
----------------
|
||||||
|
|
||||||
|
The OpenStack Summit happens during this week in Vancouver, BC. It will
|
||||||
|
include a "Forum" in which people from all parts of our community will gather
|
||||||
|
to give feedback on the last release (Queens) and discuss requirements for the
|
||||||
|
next development cycle (S).
|
||||||
|
|
||||||
|
.. _r-2:
|
||||||
|
|
||||||
|
Rocky-2 milestone
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
7 June 2018 is the Rocky-2 milestone window for projects following the
|
||||||
|
`release:cycle-with-milestones`_ model.
|
||||||
|
|
||||||
|
.. _r-final-lib:
|
||||||
|
|
||||||
|
Final release for non-client libraries
|
||||||
|
--------------------------------------
|
||||||
|
|
||||||
|
Libraries that are not client libraries (Oslo and others) should issue their
|
||||||
|
final release during this week. That allows to give time for last-minute
|
||||||
|
changes before feature freeze.
|
||||||
|
|
||||||
|
.. _r-3:
|
||||||
|
|
||||||
|
Rocky-3 milestone
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
26 July 2018 is the Rocky-3 milestone window for projects following the
|
||||||
|
`release:cycle-with-milestones`_ model.
|
||||||
|
|
||||||
|
.. _r-goals-complete:
|
||||||
|
|
||||||
|
Rocky Community Goals Completed
|
||||||
|
-------------------------------
|
||||||
|
|
||||||
|
Teams should prepare their documentation for completing `the
|
||||||
|
community-wide goals for Rocky
|
||||||
|
<https://governance.openstack.org/tc/goals/rocky/index.html>`__.
|
||||||
|
|
||||||
|
.. _r-extra-atcs:
|
||||||
|
|
||||||
|
Extra-ATCs deadline
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
Project teams should identify contributors who have had a significant
|
||||||
|
impact this cycle but who would not qualify for ATC status using the
|
||||||
|
regular process because they have not submitted a patch. Those names
|
||||||
|
should be added to the governance repo for consideration as ATC for
|
||||||
|
the future.
|
||||||
|
|
||||||
|
.. _r-ff:
|
||||||
|
|
||||||
|
Feature freeze
|
||||||
|
--------------
|
||||||
|
|
||||||
|
The Rocky-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.
|
||||||
|
|
||||||
|
.. _r-rf:
|
||||||
|
|
||||||
|
Requirements freeze
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
After the Rocky-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.
|
||||||
|
|
||||||
|
.. _r-final-clientlib:
|
||||||
|
|
||||||
|
Final release for client libraries
|
||||||
|
----------------------------------
|
||||||
|
|
||||||
|
Client libraries should issue their final release during this week, to
|
||||||
|
match feature freeze.
|
||||||
|
|
||||||
|
.. _r-soft-sf:
|
||||||
|
|
||||||
|
Soft StringFreeze
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
You are no longer allowed to accept proposed changes containing
|
||||||
|
modifications in user-facing strings. Such changes should be rejected
|
||||||
|
by the review team and postponed until the next series development
|
||||||
|
opens (which should happen when RC1 is published).
|
||||||
|
|
||||||
|
.. _r-mf:
|
||||||
|
|
||||||
|
Membership Freeze
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
Projects must participate in at least two milestones in order to be
|
||||||
|
considered part of the release. Projects made official after the
|
||||||
|
second milestone, or which fail to produce milestone releases for at
|
||||||
|
least one of the first and second milestones as well as the third
|
||||||
|
milestone, are therefore not considered part of the release for the
|
||||||
|
cycle.
|
||||||
|
|
||||||
|
.. _r-rc1:
|
||||||
|
|
||||||
|
RC1 target week
|
||||||
|
---------------
|
||||||
|
|
||||||
|
The week of 6 August 2018 is the target date for projects following the
|
||||||
|
`release:cycle-with-milestones`_ model to issue their first release candidate,
|
||||||
|
with a deadline of 9 August 2018.
|
||||||
|
|
||||||
|
.. _r-hard-sf:
|
||||||
|
|
||||||
|
Hard StringFreeze
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
This happens when the RC1 for the project is tagged. At this point, ideally
|
||||||
|
no strings are changed (or added, or removed), to give translator time to
|
||||||
|
finish up their efforts.
|
||||||
|
|
||||||
|
.. _r-finalrc:
|
||||||
|
|
||||||
|
Final RCs and intermediary releases
|
||||||
|
-----------------------------------
|
||||||
|
|
||||||
|
The week of 20 August 2018 is the last week to issue release candidates or
|
||||||
|
intermediary releases before release week. During release week, only
|
||||||
|
final-release-critical releases will be accepted (at the discretion of
|
||||||
|
the release team).
|
||||||
|
|
||||||
|
.. _r-release:
|
||||||
|
|
||||||
|
Rocky release
|
||||||
|
-------------
|
||||||
|
|
||||||
|
The Rocky coordinated release will happen on 30 August 2018.
|
||||||
|
|
||||||
|
.. _r-trailing-ff:
|
||||||
|
|
||||||
|
Rocky cycle-trailing feature freeze
|
||||||
|
-----------------------------------
|
||||||
|
|
||||||
|
The release deadline for projects using the release:cycle-trailing model that
|
||||||
|
follow the main release cycle.
|
||||||
|
|
||||||
|
.. _r-trailing-rc:
|
||||||
|
|
||||||
|
Rocky cycle-trailing RC deadline
|
||||||
|
--------------------------------
|
||||||
|
|
||||||
|
The deadline for publishing a first release candidate for projects using the
|
||||||
|
release:cycle-trailing model that follow the main release cycle.
|
||||||
|
|
||||||
|
.. _r-trailing-release:
|
||||||
|
|
||||||
|
Rocky cycle-trailing release deadline
|
||||||
|
-------------------------------------
|
||||||
|
|
||||||
|
The release deadline for projects using the release:cycle-trailing model that
|
||||||
|
follow the main release cycle.
|
||||||
|
|
||||||
|
|
||||||
|
Project-specific events
|
||||||
|
=======================
|
||||||
|
|
||||||
|
Elections
|
||||||
|
---------
|
||||||
124
doc/source/rocky/schedule.yaml
Normal file
124
doc/source/rocky/schedule.yaml
Normal file
@@ -0,0 +1,124 @@
|
|||||||
|
---
|
||||||
|
cycle:
|
||||||
|
- end: '2018-03-02'
|
||||||
|
start: '2018-02-26'
|
||||||
|
x-project:
|
||||||
|
- q-release
|
||||||
|
- r-ptg
|
||||||
|
- r-goals-research
|
||||||
|
- end: '2018-03-09'
|
||||||
|
name: R-25
|
||||||
|
start: '2018-03-05'
|
||||||
|
- end: '2018-03-16'
|
||||||
|
name: R-24
|
||||||
|
start: '2018-03-12'
|
||||||
|
- end: '2018-03-23'
|
||||||
|
name: R-23
|
||||||
|
start: '2018-03-19'
|
||||||
|
- end: '2018-03-30'
|
||||||
|
name: R-22
|
||||||
|
start: '2018-03-26'
|
||||||
|
- end: '2018-04-06'
|
||||||
|
name: R-21
|
||||||
|
start: '2018-04-02'
|
||||||
|
- end: '2018-04-13'
|
||||||
|
name: R-20
|
||||||
|
start: '2018-04-09'
|
||||||
|
- end: '2018-04-20'
|
||||||
|
name: 'R-19'
|
||||||
|
start: '2018-04-16'
|
||||||
|
x-project:
|
||||||
|
- r-1
|
||||||
|
- end: '2018-04-27'
|
||||||
|
name: R-18
|
||||||
|
start: '2018-04-23'
|
||||||
|
- end: '2018-05-04'
|
||||||
|
name: R-17
|
||||||
|
start: '2018-04-30'
|
||||||
|
- end: '2018-05-11'
|
||||||
|
name: R-16
|
||||||
|
start: '2018-05-07'
|
||||||
|
- end: '2018-05-18'
|
||||||
|
name: R-15
|
||||||
|
start: '2018-05-14'
|
||||||
|
- end: '2018-05-25'
|
||||||
|
name: R-14
|
||||||
|
start: '2018-05-21'
|
||||||
|
x-project:
|
||||||
|
- r-summit
|
||||||
|
- end: '2018-06-01'
|
||||||
|
name: R-13
|
||||||
|
start: '2018-05-28'
|
||||||
|
- end: '2018-06-08'
|
||||||
|
name: R-12
|
||||||
|
start: '2018-06-04'
|
||||||
|
x-project:
|
||||||
|
- r-2
|
||||||
|
- r-mf
|
||||||
|
- end: '2018-06-15'
|
||||||
|
name: R-11
|
||||||
|
start: '2018-06-11'
|
||||||
|
- end: '2018-06-22'
|
||||||
|
name: R-10
|
||||||
|
start: '2018-06-18'
|
||||||
|
- end: '2018-06-29'
|
||||||
|
name: R-9
|
||||||
|
start: '2018-06-25'
|
||||||
|
- end: '2018-07-06'
|
||||||
|
name: R-8
|
||||||
|
start: '2018-07-02'
|
||||||
|
- end: '2018-07-13'
|
||||||
|
name: R-7
|
||||||
|
start: '2018-07-09'
|
||||||
|
x-project:
|
||||||
|
- r-extra-atcs
|
||||||
|
- end: '2018-07-20'
|
||||||
|
name: R-6
|
||||||
|
start: '2018-07-16'
|
||||||
|
x-project:
|
||||||
|
- r-final-lib
|
||||||
|
- end: '2018-07-27'
|
||||||
|
name: R-5
|
||||||
|
start: '2018-07-23'
|
||||||
|
x-project:
|
||||||
|
- r-3
|
||||||
|
- r-ff
|
||||||
|
- r-final-clientlib
|
||||||
|
- r-soft-sf
|
||||||
|
- r-rf
|
||||||
|
- r-goals-complete
|
||||||
|
- end: '2018-08-03'
|
||||||
|
name: R-4
|
||||||
|
start: '2018-07-30'
|
||||||
|
- end: '2018-08-10'
|
||||||
|
name: R-3
|
||||||
|
start: '2018-08-06'
|
||||||
|
x-project:
|
||||||
|
- r-rc1
|
||||||
|
- r-hard-sf
|
||||||
|
- r-trailing-ff
|
||||||
|
- end: '2018-08-17'
|
||||||
|
name: R-2
|
||||||
|
start: '2018-08-13'
|
||||||
|
- end: '2018-08-24'
|
||||||
|
name: R-1
|
||||||
|
start: '2018-08-20'
|
||||||
|
x-project:
|
||||||
|
- r-finalrc
|
||||||
|
- end: '2018-08-31'
|
||||||
|
name: R-0
|
||||||
|
start: '2018-08-27'
|
||||||
|
x-project:
|
||||||
|
- r-release
|
||||||
|
- r-trailing-rc
|
||||||
|
- end: '2018-09-07'
|
||||||
|
name: R+1
|
||||||
|
start: '2018-09-03'
|
||||||
|
- end: '2018-09-14'
|
||||||
|
name: R+2
|
||||||
|
start: '2018-09-10'
|
||||||
|
x-project:
|
||||||
|
- r-trailing-release
|
||||||
|
release-week: 2018-08-27
|
||||||
|
start-week: 2018-03-05
|
||||||
|
|
||||||
Reference in New Issue
Block a user