Proposed release schedule for Stein

This is a proposed schedule for the Stein release extending
the cycle to 32 weeks to align with a combined Summit/PTG
event in March 2019.

Change-Id: Ic84a3a87d8ef53ae839a2c65cb553cf926f7663f

doc/source/index.rst

@@ -22,6 +22,7 @@ updates.
    :maxdepth: 1
    :hidden:
 
+   stein/index
    rocky/index
    queens/index
    pike/index

doc/source/stein/highlights.rst

@@ -0,0 +1,7 @@
+========================
+Stein Release Highlights
+========================
+
+.. serieshighlights::
+   :series: stein
+

doc/source/stein/index.rst

@@ -0,0 +1,20 @@
+=====
+Stein
+=====
+
+Projected Release Date: 11 April, 2019
+
+.. toctree::
+   :maxdepth: 1
+
+
+   schedule
+
+.. toctree::
+   :hidden:
+
+   highlights
+
+
+.. deliverable::
+   :series: stein

doc/source/stein/schedule.rst

@@ -0,0 +1,204 @@
+=======================
+ Stein Release Schedule
+=======================
+
+3 September 2018 - 8 April 2019 (32 weeks)
+
+.. datatemplate::
+   :source: schedule.yaml
+   :template: schedule_table.tmpl
+
+.. ics::
+   :source: schedule.yaml
+   :name: Stein
+
+`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. Exceptions to this policy will be explicitly mentioned in the
+   event description.
+
+Cross-project events
+====================
+
+.. _s-goals-research:
+
+Stein Goals Research
+--------------------
+
+Pre-cycle planning and investigation into `the community-wide goals
+for Stein <https://governance.openstack.org/tc/goals/stein/index.html>`__.
+
+.. _s-ptg:
+
+Stein Project Team Gathering (PTG)
+----------------------------------
+
+`Project team gathering <https://www.openstack.org/ptg>`__ for the Stein
+cycle 10 - 14 September in Denver, Colorado, USA.
+
+.. _s-1:
+
+Stein-1 milestone
+-----------------
+
+25 October 2018 is the Stein-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
+
+.. _s-goals-ack:
+
+Stein Community Goals Acknowledgement
+-------------------------------------
+
+Teams should prepare their acknowledgement of `the community-wide
+goals for
+<https://governance.openstack.org/tc/goals/stein/index.html>`__.
+
+.. _s-summit:
+
+OpenStack Summit
+----------------
+
+The OpenStack Summit happens during this week in Berlin, Germany. It will
+include a "Forum" in which people from all parts of our community will gather
+to give feedback on the last release (Rocky) and discuss requirements for the
+next development cycle (Stein).
+
+.. _s-2:
+
+Stein-2 milestone
+-----------------
+
+10 January 2019 is the Stein-2 milestone window for projects following the
+`release:cycle-with-milestones`_ model.
+
+.. _s-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.
+
+.. _s-3:
+
+Stein-3 milestone
+-----------------
+
+28 February 2019 is the Stein-3 milestone window for projects following the
+`release:cycle-with-milestones`_ model.
+
+.. _s-goals-complete:
+
+Stein Community Goals Completed
+-------------------------------
+
+Teams should prepare their documentation for completing `the
+community-wide goals for Stein
+<https://governance.openstack.org/tc/goals/stein/index.html>`__.
+
+.. _s-ff:
+
+Feature freeze
+--------------
+
+The Stein-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.
+
+.. _s-rf:
+
+Requirements freeze
+-------------------
+
+After the Stein-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.
+
+.. _s-final-clientlib:
+
+Final release for client libraries
+----------------------------------
+
+Client libraries should issue their final release during this week, to match
+feature freeze.
+
+.. _s-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).
+
+.. _s-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. This does not apply to cycle-trailing
+packaging / lifecycle management projects.
+
+.. _s-rc1:
+
+RC1 target week
+---------------
+
+The week of 18 March 2019 is the target date for projects following the
+`release:cycle-with-milestones`_ model to issue their first release candidate,
+with a deadline of 21 March 2019.
+
+.. _s-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.
+
+.. _s-finalrc:
+
+Final RCs and intermediary releases
+-----------------------------------
+
+The week of 1 April 2019 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).
+
+.. _s-release:
+
+Stein release
+-------------
+
+The Stein coordinated release will happen on 11 April 2019.
+
+.. _s-trailing-release:
+
+Stein cycle-trailing release deadline
+-------------------------------------
+
+The release deadline for projects using the release:cycle-trailing model that
+follow the main release cycle is set to 13 June, 2019.
+
+Project-specific events
+=======================
+
+PTL Elections
+-------------
+

doc/source/stein/schedule.yaml

@@ -0,0 +1,131 @@
+---
+start-week: 2018-09-03
+release-week: 2019-04-08
+cycle:
+- end: '2018-08-31'
+  start: '2018-08-27'
+  x-project:
+    - r-release
+    - s-goals-research
+- end: '2018-09-07'
+  name: R-31
+  start: '2018-09-03'
+- end: '2018-09-14'
+  name: R-30
+  start: '2018-09-10'
+  x-project:
+    - s-ptg
+- end: '2018-09-21'
+  name: R-29
+  start: '2018-09-17'
+- end: '2018-09-28'
+  name: R-28
+  start: '2018-09-24'
+- end: '2018-10-05'
+  name: R-27
+  start: '2018-10-01'
+- end: '2018-10-12'
+  name: R-26
+  start: '2018-10-08'
+- end: '2018-10-19'
+  name: R-25
+  start: '2018-10-15'
+- end: '2018-10-26'
+  name: R-24
+  start: '2018-10-22'
+  x-project:
+    - s-1
+- end: '2018-11-02'
+  name: R-23
+  start: '2018-10-29'
+- end: '2018-11-09'
+  name: R-22
+  start: '2018-11-05'
+  x-project:
+    - s-summit
+- end: '2018-11-16'
+  name: R-21
+  start: '2018-11-12'
+- end: '2018-11-23'
+  name: R-20
+  start: '2018-11-19'
+- end: '2018-11-30'
+  name: R-19
+  start: '2018-11-26'
+- end: '2018-12-07'
+  name: R-18
+  start: '2018-12-03'
+- end: '2018-12-14'
+  name: R-17
+  start: '2018-12-10'
+- end: '2018-12-21'
+  name: R-16
+  start: '2018-12-17'
+- end: '2018-12-28'
+  name: R-15
+  start: '2018-12-24'
+- end: '2019-01-04'
+  name: R-14
+  start: '2018-12-31'
+- end: '2019-01-11'
+  name: R-13
+  start: '2019-01-07'
+  x-project:
+    - s-2
+    - s-mf
+- end: '2019-01-18'
+  name: R-12
+  start: '2019-01-14'
+- end: '2019-01-25'
+  name: R-11
+  start: '2019-01-21'
+- end: '2019-02-01'
+  name: R-10
+  start: '2019-01-28'
+- end: '2019-02-08'
+  name: R-9
+  start: '2019-02-04'
+- end: '2019-02-15'
+  name: R-8
+  start: '2019-02-11'
+- end: '2019-02-22'
+  name: R-7
+  start: '2019-02-18'
+- end: '2019-03-01'
+  name: R-6
+  start: '2019-02-25'
+  x-project:
+    - s-final-lib
+- end: '2019-03-08'
+  name: R-5
+  start: '2019-03-04'
+  x-project:
+    - s-3
+    - s-ff
+    - s-final-clientlib
+    - s-soft-sf
+    - s-rf
+    - s-goals-complete
+- end: '2019-03-15'
+  name: R-4
+  start: '2019-03-11'
+- end: '2019-03-22'
+  name: R-3
+  start: '2019-03-18'
+  x-project:
+    - s-rc1
+    - s-hard-sf
+- end: '2019-03-29'
+  name: R-2
+  start: '2019-03-25'
+- end: '2019-04-05'
+  name: R-1
+  start: '2019-04-01'
+  x-project:
+    - s-finalrc
+- end: '2019-04-12'
+  name: R+0
+  start: '2019-04-08'
+  x-project:
+  - s-release
+