Train Release Schedule
Train Release Schedule¶
15 April 2019 - 16 October 2019 (27 weeks)
Week |
Cross-project events |
Project-specific events |
|
|---|---|---|---|
Apr 08 - Apr 12 |
|||
Apr 15 - Apr 19 |
R-26 |
||
Apr 22 - Apr 26 |
R-25 |
||
Apr 29 - May 03 |
R-24 |
||
May 06 - May 10 |
R-23 |
||
May 13 - May 17 |
R-22 |
||
May 20 - May 24 |
R-21 |
||
May 27 - May 31 |
R-20 |
||
Jun 03 - Jun 07 |
R-19 |
||
Jun 10 - Jun 14 |
R-18 |
||
Jun 17 - Jun 21 |
R-17 |
||
Jun 24 - Jun 28 |
R-16 |
||
Jul 01 - Jul 05 |
R-15 |
||
Jul 08 - Jul 12 |
R-14 |
||
Jul 15 - Jul 19 |
R-13 |
||
Jul 22 - Jul 26 |
R-12 |
||
Jul 29 - Aug 02 |
R-11 |
||
Aug 05 - Aug 09 |
R-10 |
||
Aug 12 - Aug 16 |
R-9 |
||
Aug 19 - Aug 23 |
R-8 |
||
Aug 26 - Aug 30 |
R-7 |
||
Sep 02 - Sep 06 |
R-6 |
||
Sep 09 - Sep 13 |
R-5 |
||
Sep 16 - Sep 20 |
R-4 |
||
Sep 23 - Sep 27 |
R-3 |
||
Sep 30 - Oct 04 |
R-2 |
||
Oct 07 - Oct 11 |
R-1 |
||
Oct 14 - Oct 18 |
R+0 |
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¶
Train Goals Research¶
Pre-cycle planning and investigation into the community-wide goals for Train.
Train-1 milestone¶
6 June, 2019 is the Train-1 milestone. See project-specific notes for relevant deadlines.
Train Community Goals Acknowledgement¶
Teams should prepare their acknowledgement of the community-wide goals for.
Open Infrastructure Summit¶
The Open Infrastructure Summit happens during this week in Denver, CO, USA. 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 (Train).
Train-2 milestone¶
25 July, 2019 is the Train-2 milestone. See project-specific notes for relevant deadlines.
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.
Train-3 milestone¶
12 September, 2019 is the Train-3 milestone. See project-specific notes for relevant deadlines.
Train Community Goals Completed¶
Teams should prepare their documentation for completing the community-wide goals for Train.
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.
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.
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.
Final release for client libraries¶
Client libraries should issue their final release during this week, to match feature freeze.
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).
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.
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.
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.
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).
Cycle highlights marketing deadline¶
Cycle highlights need to be added to the release deliverables by feature freeze to be included in any marketing release messaging. Highlights may be added after this point, but they will likely only be useful for historical purposes.
See the project team guide for more details and instructions on adding these highlights.
Election Email Deadline¶
Contributors that will be in the electorate for the upcoming elections should confirm their gerrit email addresses by this date (September 3rd, 2019 at 00:00 UTC). Electorate rolls are generated after this date and ballots will be sent to the listed gerrit email address.
TC Elections¶
TC Election Nomination Begins¶
Technical committee candidates interested in serving for the next calendar year should announce their candidacies and platforms during this week. Please see the Election site for specific timing imformation.
TC Election Campaigning Begins¶
The electorate has time to ask candidates questions about their platforms and debate topics before polling begins. Please see the Election site for specific timing information.
TC Election Polling Begins¶
Election polling week for open seats on the TC. Please see the Election site for specific timing imformation.
Train release¶
The Train coordinated release will happen on 16 October 2019.
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¶
‘U’ PTL self-nomination¶
Project team lead candidates for the ‘U’ cycle should announce their candidacy during this week. Refer to the Election Site for exact details.
‘U’ PTL Election Polling Begins¶
Election week for Project team leads (where an election must be held to determine the winner). Refer to the Election Site for exact details.
Keystone¶
Keystone Spec Proposal Freeze¶
All Keystone specs targeted to Train must be submitted to the keystone-specs repository by the end of the week.
Keystone Spec Freeze¶
All Keystone specs targeted to Train must be approved by the end of the week.
Keystone Feature Proposal Freeze¶
All new Keystone features must be proposed and substantially completed, with unit tests and documentation by the end of the week.
Keystone Feature Freeze¶
All new Keystone features must be merged by the end of the week.
Nova¶
Nova Spec Freeze¶
All Nova specs targeted to Train must be approved by Thursday.
Nova Feature Freeze¶
All new Nova features must be approved by Thursday.
Oslo¶
Oslo Feature Freeze¶
All new Oslo features must be proposed and substantially complete, with unit tests by the end of the week.
Manila¶
Manila Spec Freeze¶
All Manila specs targeted to Train must be approved by the end of the week.
Manila Driver Deadline¶
By the end of the week all new backend drivers for Manila must be substantially complete, with unit tests, and passing 3rd party CI. Drivers do not have to actually merge until feature freeze.
Manila Feature Proposal Freeze¶
All new Manila features must be proposed and substantially completed, with unit tests and documentation by the end of the week.
Manila Feature Freeze¶
All new Manila features must be merged by the end of the week.
Cinder¶
Cinder Spec Freeze¶
All Cinder Specs must be approved by 25 Jul 2019 (23:59 UTC).
Cinder New Driver Merge Deadline¶
The deadline for merging a new backend driver to Cinder is 25 Jul 2019 (23:59 UTC). New drivers must be complete with unit tests at this point in time. The backend driver must also have a 3rd Party CI running reliably and the driver must be merged at this point to be included in the Train release.
Cinder New Target Driver Merge Deadline¶
The deadline for merging a new target driver to Cinder is 25 Jul 2019 (23:59 UTC). New target drivers must be complete with unit tests at this point in time. The target driver must also have a 3rd Party CI running reliably and the target driver must be merged at this point to be included in the Train release.
Cinder 3rd Party CIs Running Py37¶
In preparation for OpenStack’s move to Python 3.x we are requiring that all vendors demonstrate their driver running Py37 tests by 25 Jul 2019 (23:59 UTC). Vendors who do not meet this reuqirement will have a patch marking their driver as unsupported submitted.
Cinder 3rd Party CIs Passing Py37 Testing¶
All vendors must demonstrate that their driver can execute 3rd Party CI with Py37 by 12 Sep 2019 (23:59 UTC) or their driver will be marked as unsupported.
Cinder Feature Proposal Freeze¶
All new Cinder features must be proposed and substantially complete with unit tests by 12 Sep 2019 (23:59 UTC).
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.