Pike release schedule

PTG2 is now 99% sure to happen on Sept 11-15 week. Here is the
proposed schedule for the Pike cycle.

Change-Id: Id022410613a851d7f0da1f78ec583d21f30c7e55

doc/source/index.rst

@@ -25,7 +25,7 @@ updates.
      * TBD
      * TBD
    - * :doc:`pike/index`
-     * *Future*
+     * :doc:`Future <pike/schedule>`
      * TBD
      * TBD
    - * :doc:`ocata/index`

doc/source/pike/schedule.rst

@@ -1,13 +1,26 @@
-========================
+=======================
  Pike Release Schedule
-========================
+=======================
+
+20 February 2017 - 1 September 2017 (27 weeks)
+
+.. datatemplate::
+   :source: schedule.yaml
+   :template: schedule_table.tmpl
+
+.. ics::
+   :source: schedule.yaml
+   :name: Pike
+
+`Subscribe to iCalendar file <schedule.ics>`__
 
 .. note::
 
-   All deadlines are generally the Thursday of the week on which they
-   are noted above. For example, the Feature Freeze in week XXX is on
-   XXX. Exceptions to this policy will be explicitly mentioned
-   in the event description.
+   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 27 July. Exceptions to this policy will be explicitly
+   mentioned in the event description.
 
 Cross-project events
 ====================
@@ -20,14 +33,6 @@ Pike Goals Research
 Pre-cycle planning and investigation into `the community-wide goals
 for Pike <https://governance.openstack.org/tc/goals/pike/index.html>`__.
 
-.. _p-design-summit:
-
-Pike Design Summit
-------------------
-
-`Feedback and requirements Forum in Boston
-<https://www.openstack.org/summit/boston-2017/>`__
-
 .. _p-ptg:
 
 Pike Project Team Gathering (PTG)
@@ -46,6 +51,25 @@ XXX is the Pike-1 milestone window for projects following the
 
 .. _release:cycle-with-milestones: https://governance.openstack.org/tc/reference/tags/release_cycle-with-milestones.html
 
+.. _p-goals-ack:
+
+Pike Community Goals Acknowledgement
+------------------------------------
+
+Teams should prepare their acknowledgement of `the community-wide
+goals for Pike
+<https://governance.openstack.org/tc/goals/pike/index.html>`__.
+
+.. _p-summit:
+
+OpenStack Summit
+----------------
+
+The OpenStack Summit happens during this week in Boston, USA. It will include
+a "Forum" in which people from all parts of our community will gather to give
+feedback on the last release (Ocata) and discuss requirements for the next
+development cycle (Queens).
+
 .. _p-2:
 
 Pike-2 milestone
@@ -71,6 +95,15 @@ Pike-3 milestone
 XXX is the Pike-3 milestone window for projects following the
 `release:cycle-with-milestones`_ model.
 
+.. _p-goals-complete:
+
+Pike Community Goals Completed
+------------------------------
+
+Teams should prepare their documentation for completing `the
+community-wide goals for Pike
+<https://governance.openstack.org/tc/goals/pike/index.html>`__.
+
 .. _p-extra-atcs:
 
 Extra-ATCs deadline
@@ -185,37 +218,3 @@ follow the main release cycle.
 Project-specific events
 =======================
 
-Elections
----------
-
-.. _q-ptl-nomination:
-
-Queens PTLs self-nomination
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Project team lead candidates for the Pike cycle should announce their
-candidacy during this week.
-
-.. _q-ptl-election:
-
-Queens cycle PTLs election
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Election week for Project team leads (where an election must be held to
-determine the winner).
-
-.. _q-tc-nomination:
-
-TC member self-nomination
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Candidates for the partial Technical Committee member renewal should announce
-their candidacy during this week.
-
-.. _q-tc-election:
-
-TC member election
-^^^^^^^^^^^^^^^^^^
-
-Election for partially renewing Technical Committee members will happen
-during this week.

doc/source/pike/schedule.yaml

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