Proposed release schedule for Train
This is a proposed schedule for the Train release. Change-Id: Id2b50afa05a2b94da9d92520ba7f49a153973276 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This commit is contained in:
parent
3f967cdd78
commit
aa70e7d786
@ -1,4 +1,10 @@
|
||||
---
|
||||
- name: train
|
||||
status: future
|
||||
initial-release: 2019-10-16
|
||||
next-phase:
|
||||
status: development
|
||||
date: 2019-04-11
|
||||
- name: stein
|
||||
status: development
|
||||
initial-release: 2019-04-10
|
||||
|
@ -22,6 +22,7 @@ updates.
|
||||
:maxdepth: 1
|
||||
:hidden:
|
||||
|
||||
train/index
|
||||
stein/index
|
||||
rocky/index
|
||||
queens/index
|
||||
|
6
doc/source/train/highlights.rst
Normal file
6
doc/source/train/highlights.rst
Normal file
@ -0,0 +1,6 @@
|
||||
========================
|
||||
Train Release Highlights
|
||||
========================
|
||||
|
||||
.. serieshighlights::
|
||||
:series: train
|
19
doc/source/train/index.rst
Normal file
19
doc/source/train/index.rst
Normal file
@ -0,0 +1,19 @@
|
||||
=====
|
||||
Train
|
||||
=====
|
||||
|
||||
Projects Release Date: 16 October, 2019
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
schedule
|
||||
|
||||
.. toctree::
|
||||
:hidden:
|
||||
|
||||
highlights
|
||||
|
||||
.. deliverable::
|
||||
:series: train
|
||||
|
203
doc/source/train/schedule.rst
Normal file
203
doc/source/train/schedule.rst
Normal file
@ -0,0 +1,203 @@
|
||||
======================
|
||||
Train Release Schedule
|
||||
======================
|
||||
|
||||
15 April 2019 - 16 October 2019 (27 weeks)
|
||||
|
||||
.. datatemplate::
|
||||
:source: schedule.yaml
|
||||
:template: schedule_table.tmpl
|
||||
|
||||
.. ics::
|
||||
:source: schedule.yaml
|
||||
:name: Train
|
||||
|
||||
`Subscribe to iCalendar file <schedule.ics>`_
|
||||
|
||||
.. note::
|
||||
|
||||
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
|
||||
====================
|
||||
|
||||
.. _t-goals-research:
|
||||
|
||||
Train Goals Research
|
||||
--------------------
|
||||
|
||||
Pre-cycle planning and investigation into `the community-wide goals
|
||||
for Train <https://governance.openstack.org/tc/goals/train/index.html>`__.
|
||||
|
||||
.. _t-1:
|
||||
|
||||
Train-1 milestone
|
||||
-----------------
|
||||
|
||||
6 June, 2019 is the Train-1 milestone. See project-specific notes for relevant
|
||||
deadlines.
|
||||
|
||||
.. _t-goals-ack:
|
||||
|
||||
Train Community Goals Acknowledgement
|
||||
-------------------------------------
|
||||
|
||||
Teams should prepare their acknowledgement of `the community-wide
|
||||
goals for
|
||||
<https://governance.openstack.org/tc/goals/train/index.html>`__.
|
||||
|
||||
.. _t-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 (Stein) and discuss requirements
|
||||
for the next development cycle (U).
|
||||
|
||||
.. _t-2:
|
||||
|
||||
Train-2 milestone
|
||||
-----------------
|
||||
|
||||
25 July, 2019 is the Train-2 milestone. See project-specific notes for relevant
|
||||
deadlines.
|
||||
|
||||
.. _t-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.
|
||||
|
||||
.. _t-3:
|
||||
|
||||
Train-3 milestone
|
||||
-----------------
|
||||
|
||||
12 September, 2019 is the Train-3 milestone. See project-specific notes for
|
||||
relevant deadlines.
|
||||
|
||||
.. _t-goals-complete:
|
||||
|
||||
Train Community Goals Completed
|
||||
-------------------------------
|
||||
|
||||
Teams should prepare their documentation for completing `the
|
||||
community-wide goals for Train
|
||||
<https://governance.openstack.org/tc/goals/train/index.html>`__.
|
||||
|
||||
.. _t-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.
|
||||
|
||||
.. _t-ff:
|
||||
|
||||
Feature freeze
|
||||
--------------
|
||||
|
||||
The Train-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
|
||||
|
||||
.. _t-rf:
|
||||
|
||||
Requirements freeze
|
||||
-------------------
|
||||
|
||||
After the Train-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.
|
||||
|
||||
.. _t-final-clientlib:
|
||||
|
||||
Final release for client libraries
|
||||
----------------------------------
|
||||
|
||||
Client libraries should issue their final release during this week, to match
|
||||
feature freeze.
|
||||
|
||||
.. _t-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).
|
||||
|
||||
.. _t-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.
|
||||
|
||||
.. _t-rc1:
|
||||
|
||||
RC1 target week
|
||||
---------------
|
||||
|
||||
The week of September 23-27 is the target date for projects following the
|
||||
`release:cycle-with-rc`_ model to issue their first release candidate.
|
||||
|
||||
.. _t-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.
|
||||
|
||||
.. _t-finalrc:
|
||||
|
||||
Final RCs and intermediary releases
|
||||
-----------------------------------
|
||||
|
||||
The week of October 7-11 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).
|
||||
|
||||
.. _t-final:
|
||||
|
||||
Train release
|
||||
-------------
|
||||
|
||||
The Train coordinated release will happen on 16 October 2019.
|
||||
|
||||
.. _t-trailing-release:
|
||||
|
||||
Train cycle-trailing release deadline
|
||||
-------------------------------------
|
||||
|
||||
The release deadline for projects using the release:cycle-trailing model that
|
||||
follow the main release cycle is set to 17 December, 2019.
|
||||
|
||||
Project-specific events
|
||||
=======================
|
||||
|
||||
PTL Elections
|
||||
-------------
|
||||
|
116
doc/source/train/schedule.yaml
Normal file
116
doc/source/train/schedule.yaml
Normal file
@ -0,0 +1,116 @@
|
||||
---
|
||||
start-week: 2019-04-15
|
||||
release-week: 2019-10-14
|
||||
cycle:
|
||||
- end: '2019-04-12'
|
||||
start: '2019-04-08'
|
||||
x-project:
|
||||
- s-release
|
||||
- t-goals-research
|
||||
- end: '2019-04-19'
|
||||
name: R-26
|
||||
start: '2019-04-15'
|
||||
- end: '2019-04-26'
|
||||
name: R-25
|
||||
start: '2019-04-22'
|
||||
- end: '2019-05-03'
|
||||
name: R-24
|
||||
start: '2019-04-29'
|
||||
x-project:
|
||||
- t-summit
|
||||
- end: '2019-05-10'
|
||||
name: R-23
|
||||
start: '2019-05-06'
|
||||
- end: '2019-05-17'
|
||||
name: R-22
|
||||
start: '2019-05-13'
|
||||
- end: '2019-05-24'
|
||||
name: R-21
|
||||
start: '2019-05-20'
|
||||
- end: '2019-05-31'
|
||||
name: R-20
|
||||
start: '2019-05-27'
|
||||
- end: '2019-06-07'
|
||||
name: R-19
|
||||
start: '2019-06-03'
|
||||
x-project:
|
||||
- t-1
|
||||
- end: '2019-06-14'
|
||||
name: R-18
|
||||
start: '2019-06-10'
|
||||
- end: '2019-06-21'
|
||||
name: R-17
|
||||
start: '2019-06-17'
|
||||
- end: '2019-06-28'
|
||||
name: R-16
|
||||
start: '2019-06-24'
|
||||
- end: '2019-07-05'
|
||||
name: R-15
|
||||
start: '2019-07-01'
|
||||
- end: '2019-07-12'
|
||||
name: R-14
|
||||
start: '2019-07-08'
|
||||
- end: '2019-07-19'
|
||||
name: R-13
|
||||
start: '2019-07-15'
|
||||
- end: '2019-07-26'
|
||||
name: R-12
|
||||
start: '2019-07-22'
|
||||
x-project:
|
||||
- t-2
|
||||
- t-mf
|
||||
- end: '2019-08-02'
|
||||
name: R-11
|
||||
start: '2019-07-29'
|
||||
- end: '2019-08-09'
|
||||
name: R-10
|
||||
start: '2019-08-05'
|
||||
- end: '2019-08-16'
|
||||
name: R-9
|
||||
start: '2019-08-12'
|
||||
- end: '2019-08-23'
|
||||
name: R-8
|
||||
start: '2019-08-19'
|
||||
- end: '2019-08-30'
|
||||
name: R-7
|
||||
start: '2019-08-26'
|
||||
x-project:
|
||||
- t-extra-atcs
|
||||
- end: '2019-09-06'
|
||||
name: R-6
|
||||
start: '2019-09-02'
|
||||
x-project:
|
||||
- t-final-lib
|
||||
- end: '2019-09-13'
|
||||
name: R-5
|
||||
start: '2019-09-09'
|
||||
x-project:
|
||||
- t-3
|
||||
- t-ff
|
||||
- t-final-clientlib
|
||||
- t-soft-sf
|
||||
- t-rf
|
||||
- t-goals-complete
|
||||
- end: '2019-09-20'
|
||||
name: R-4
|
||||
start: '2019-09-16'
|
||||
- end: '2019-09-27'
|
||||
name: R-3
|
||||
start: '2019-09-23'
|
||||
x-project:
|
||||
- t-rc1
|
||||
- t-hard-sf
|
||||
- end: '2019-10-04'
|
||||
name: R-2
|
||||
start: '2019-09-30'
|
||||
- end: '2019-10-11'
|
||||
name: R-1
|
||||
start: '2019-10-07'
|
||||
x-project:
|
||||
- t-finalrc
|
||||
- end: '2019-10-18'
|
||||
name: R+0
|
||||
start: '2019-10-14'
|
||||
x-project:
|
||||
- t-final
|
||||
|
Loading…
Reference in New Issue
Block a user