Proposed release schedule for Ussuri

Change-Id: Iae9761f151debe640f601375398910ad6c99e788
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>

data/series_status.yaml

@@ -1,4 +1,10 @@
 ---
+- name: ussuri
+  status: development
+  initial-release: 2020-05-13
+  next-phase:
+    status: maintained
+    date: 2020-05-13
 - name: train
   status: development
   initial-release: 2019-10-16

doc/source/_exts/ics.py

@@ -61,7 +61,7 @@ class ICS(rst.Directive):
                 last_update, '%Y-%m-%d %H:%M:%S')
             LOG.info('[ics] Last update of %s was %s',
                      rel_filename, last_update)
-        except subprocess.CalledProcessError:
+        except (subprocess.CalledProcessError, ValueError):
             self.last_update = datetime.datetime.utcnow()
 
         if data_source.endswith('.yaml'):
@@ -180,6 +180,7 @@ def doctree_resolved(app, doctree, docname):
             description = [
                 _format_description(doctree.ids[item])
                 for item in week.get('x-project', [])
+                if item in doctree.ids
             ]
             if description:
                 event.add('description', '\n\n'.join(description))

doc/source/index.rst

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

doc/source/ussuri/highlights.rst

@@ -0,0 +1,6 @@
+=========================
+Ussuri Release Highlights
+=========================
+
+.. serieshighlights::
+   :series: ussuri

doc/source/ussuri/index.rst

@@ -0,0 +1,19 @@
+======
+Ussuri
+======
+
+Projected Release Date: 13 May, 2020
+
+.. toctree::
+   :maxdepth: 1
+
+   schedule
+
+.. toctree::
+   :hidden:
+
+   highlights
+
+.. deliverable::
+   :series: ussuri
+

doc/source/ussuri/schedule.rst

@@ -0,0 +1,195 @@
+=======================
+Ussuri Release Schedule
+=======================
+
+.. note::
+
+   Deadlines are generally the Thursday of the week on which they are noted
+   below. Exceptions to this policy will be explicitly mentioned in the event
+   description.
+
+21 October 2019 - 15 May 2020 (30 weeks)
+
+.. datatemplate::
+   :source: schedule.yaml
+   :template: schedule_table.tmpl
+
+.. ics::
+   :source: schedule.yaml
+   :name: Ussuri
+
+`Subscribe to iCalendar file <schedule.ics>`_
+
+Cross-project events
+====================
+
+.. _u-goals-research:
+
+Ussuri Goals Research
+---------------------
+
+Pre-cycle planning and investigation into `the community-wide goals
+for Ussuri <https://governance.openstack.org/tc/goals/ussuri/index.html>`__.
+
+.. _u-summit:
+
+Open Infrastructure Summit
+--------------------------
+
+The Open Infrastructure Summit happens during this week in Shanghai, China. It
+will include a “Forum” in which people from all parts of our community will
+gather to give feedback on the last release (Train) and discuss requirements
+for future releases.
+
+.. _u-1:
+
+Ussuri-1 milestone
+------------------
+
+12 December, 2019 is the Ussuri-1 milestone. See project-specific notes for
+relevant deadlines.
+
+.. _u-goals-ack:
+
+Ussuri Community Goals Acknowledgement
+--------------------------------------
+
+Teams should prepare their acknowledgement of `the community-wide
+goals for Ussuri
+<https://governance.openstack.org/tc/goals/ussuri/index.html>`__.
+
+.. _u-2:
+
+Ussuri-2 milestone
+------------------
+
+13 February, 2020 is the Ussuri-2 milestone. See project-specific notes for
+relevant deadlines.
+
+.. _u-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.
+
+.. _u-3:
+
+Ussuri-3 milestone
+------------------
+
+9 April, 2020 is the Ussuri-3 milestone. See project-specific notes for
+relevant deadlines.
+
+.. _u-goals-complete:
+
+Ussuri Community Goals Completed
+--------------------------------
+
+Teams should prepare their documentation for completing `the
+community-wide goals for Ussuri
+<https://governance.openstack.org/tc/goals/ussuri/index.html>`__.
+
+.. _u-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.
+
+.. _u-ff:
+
+Feature freeze
+--------------
+
+The Ussuri-3 milestone marks feature freeze for projects following the
+`release:cycle-with-rc`_ model. No featureful patch should be landed
+after this point. Exceptions may be granted by the project PTL.
+
+.. _release:cycle-with-rc: https://releases.openstack.org/reference/release_models.html#cycle-with-rc
+
+.. _u-rf:
+
+Requirements freeze
+-------------------
+
+After the Ussuri-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.
+
+.. _u-final-clientlib:
+
+Final release for client libraries
+----------------------------------
+
+Client libraries should issue their final release during this week, to match
+feature freeze.
+
+.. _u-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).
+
+.. _u-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.
+
+.. _u-rc1:
+
+RC1 target week
+---------------
+
+The week of 20 April is the target date for projects following the
+`release:cycle-with-rc`_ model to issue their first release candidate.
+
+.. _u-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 translators time to
+finish up their efforts.
+
+.. _u-finalrc:
+
+Final RCs and intermediary releases
+-----------------------------------
+
+The week of 4 May 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).
+
+.. _u-final:
+
+Ussuri release
+--------------
+
+The Ussuri coordinated release will happen on Wednesday, 13 May, 2020.
+
+Project-specific events
+=======================
+
+PTL Elections
+-------------
+

doc/source/ussuri/schedule.yaml

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