457552a01c
Based on feedback during the fishbowl session held at the Ocata summit in Barcelona, downstream consumers of the final release would like the release to happen earlier in the week to give them time to create packages before the weekend. This change moves the final release date forward one day from Thursday 23 Feb to Wednesday 22 Feb to accommodate this request. Impact on project teams is expected to be minimal, because the release team creates the final tag based on existing release candidates. Change-Id: I91834e6b89827f928588932d3ea74f938f5d32a4 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
16 KiB
Ocata Release Schedule
31 October 2016 - 24 February 2017 (16 weeks)
| Week | Cross-project events | Project-specific events |
+============+======+===========================+=============================+
| Oct 03-07 | | n-release | | | |
+---------------------------+-----------------------------+ | | | o-goals-research | |
+------------+------+---------------------------+-----------------------------+
| Oct 10-14 | | | |
+------------+------+---------------------------+-----------------------------+
| Oct 17-21 | | | |
+------------+------+---------------------------+-----------------------------+
| Oct 24-28 | | o-design-summit | |
+------------+------+---------------------------+-----------------------------+
| Oct 31-04 | R-16 | | |
+------------+------+---------------------------+-----------------------------+
| Nov 07-11 | R-15 | | o-glance-spec-prop |
+------------+------+---------------------------+-----------------------------+
| Nov 14-18 | R-14 | o-1 | o-nova-spec-freeze | | |
+---------------------------+-----------------------------+ | | | o-goals-ack | o-manila-spec-frz1 | | |
+---------------------------+-----------------------------+ | | | |
o-key-spec-prop |
+------------+------+---------------------------+-----------------------------+
| Nov 21-25 | R-13 | | o-glance-spec-freeze | | | |
+-----------------------------+ | | | | o-trove-spec-prop |
+------------+------+---------------------------+-----------------------------+
| Nov 28-02 | R-12 | | |
+------------+------+---------------------------+-----------------------------+
| Dec 05-09 | R-11 | | |
+------------+------+---------------------------+-----------------------------+
| Dec 12-16 | R-10 | o-2 | o-trove-spec-freeze | | |
+---------------------------+-----------------------------+ | | | o-mf | o-cinder-nddeadline | | |
+---------------------------+-----------------------------+ | | | |
o-cinder-spec-freeze |
| | | +-----------------------------+ | | | | o-key-spec-freeze | | | |
+-----------------------------+ | | | | o-manila-spec-frz2 |
+------------+------+---------------------------+-----------------------------+
| Dec 19-23 | R-9 | | o-manila-drv-freeze |
+------------+------+---------------------------+-----------------------------+
| Dec 26-30 | R-8 | | o-key-feature-prop |
+------------+------+---------------------------+-----------------------------+
| Jan 02-06 | R-7 | o-extra-atcs | |
+------------+------+---------------------------+-----------------------------+
| Jan 09-13 | R-6 | | |
+------------+------+---------------------------+-----------------------------+
| Jan 16-20 | R-5 | o-final-lib | o-trove-client-soft | | |
+---------------------------+-----------------------------+ | | | |
o-trove-guest-req |
+------------+------+---------------------------+-----------------------------+
| Jan 23-27 | R-4 | o-3
| o-key-feature-freeze
| | | +---------------------------+-----------------------------+ | | |
o-ff | | | |
+---------------------------+-----------------------------+ | | | o-final-clientlib | | | |
+---------------------------+-----------------------------+ | | | o-soft-sf | | | |
+---------------------------+-----------------------------+ | | | o-rf | | | |
+---------------------------+-----------------------------+ | | | o-goals-complete | |
+------------+------+---------------------------+-----------------------------+
| Jan 30-03 | R-3 | o-rc1 | | | |
+---------------------------+-----------------------------+ | | | o-hard-sf | |
+------------+------+---------------------------+-----------------------------+
| Feb 06-10 | R-2 | | |
+------------+------+---------------------------+-----------------------------+
| Feb 13-17 | R-1 | o-finalrc | |
+------------+------+---------------------------+-----------------------------+
| Feb 20-24 | R+0 | p-ptg0 | | | |
+---------------------------+-----------------------------+ | | | o-release | |
+------------+------+---------------------------+-----------------------------+
| Feb 27-03 | R+1 | | |
+------------+------+---------------------------+-----------------------------+
| Mar 06-10 | R+2 | o-trailing | |
+------------+------+---------------------------+-----------------------------+
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. For example, the Feature Freeze in week R-4 is on 26 January. Exceptions to this policy will be explicitly mentioned in the event description.
Cross-project events
Ocata Goals Research
Pre-cycle planning and investigation into the community-wide goals for Ocata.
Ocata Design Summit
Pike Project Team Gathering (PTG)
Project team gathering for the Pike release 20-24 February 2017 in Atlanta, Georgia.
Ocata-1 milestone
17 November is the ocata-1 milestone window for projects following the release:cycle-with-milestones model.
Ocata Community Goals Acknowledgement
Teams should prepare their acknowledgement of the community-wide goals for Ocata.
Ocata-2 milestone
15 December is the ocata-2 milestone window for projects following the release:cycle-with-milestones model.
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.
Ocata-3 milestone
26 January is the ocata-3 milestone window for projects following the release:cycle-with-milestones model.
Ocata Community Goals Completed
Teams should prepare their documentation for completing the community-wide goals for Ocata.
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.
Although extra ATCs can be nominated at any point, there is a
deadline to be included in electorate for the next release cycle. The
ATC list needs to be approved by the TC by (TBD), and in order to appear
on the TC agenda to be discussed, the proposals need to be submitted to
the openstack/governance repository by (TBD).
Feature freeze
The ocata-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.
Requirements freeze
After the ocata-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.
RC1 target week
The week of 30 January - 3 February is the target date for projects following the release:cycle-with-milestones model to issue their first release candidate, with a deadline of 2 February.
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.
Final RCs and intermediary releases
The week of 13-17 February 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).
Ocata release
The Ocata coordinated release will happen on 22 February.
Ocata cycle-trailing Deadline
The deadline for projects using the release:cycle-trailing model that follow the main release cycle is 9 March.
Project-specific events
Elections
Pike PTLs self-nomination
Project team lead candidates for the Ocata cycle should announce their candidacy during this week.
Pike cycle PTLs election
Election week for Project team leads (where an election must be held to determine the winner).
TC member self-nomination
Candidates for the partial Technical Committee member renewal should announce their candidacy during this week.
TC member election
Election for partially renewing Technical Committee members will happen during this week.
Cinder
Cinder New Backend Driver Deadline
The deadline for getting a new backend driver added to Cinder is 14th December, 2016. All review issues must be addressed and third party CI must be reporting and stable with enough time for reviewers prior to the deadline. Meeting these requirements on the 14th does not guarantee core reviewers will have enough time to merge the driver.
Cinder Spec Freeze
All Cinder specs must be approved by 14th December, 2016.
Glance
The following deadlines are specific to the Glance project.
Glance Spec Proposal Freeze
All Glance, python-glanceclient, and glance_store specs must be proposed as patches to the glance-specs repository by 23:59 UTC on Thursday 10 November 2016.
Glance Spec Freeze
All Glance, python-glanceclient, and glance_store specs must be merged into the glance-specs repository by 23:59 UTC on Friday 25 November 2016.
Nova
The deadlines below are specific to the Nova project.
Nova Spec Freeze
All Nova specs must be approved by 17th November, 2016.
Manila Low-Priority Spec Freeze
All Manila specs must be approved by 17th November, 2016, unless they are officially designated high-priority.
Manila High-Priority Spec Freeze
All high-priority Manila specs must be approved by 15th December, 2016.
Manila Driver Proposal Freeze
All new Manila drivers must be proposed by 19th December, 2016.
Trove
The deadlines below are specific to the Trove project.
Trove Spec Proposal Deadline
Submit all Trove specs for the release by the end of this week (for review) in trove-specs repository.
Trove Spec Freeze
All Trove specs for the release must be approved by the end of this week.
Trove Guest Requirements Freeze:
Freeze the requirements for all guest agents by this date and make the requirements file for guests.
Trove Client Soft Freeze
All major features for the python-troveclient must be reviewed and approved by the end of this week, this gives us one additional week to address any issues with dependencies.
Keystone
The deadlines below are specific to the Keystone project.
Keystone Spec Proposal Deadline
Submit all keystone specs for the release by the end of this week (for review) in keystone-specs repository.
Keystone Spec Freeze
All keystone specs for the release must be approved by the end of this week.
Keystone Feature Proposal Deadline
All major keystone features for the release must be proposed by the end of this week.
Keystone Feature Proposal Freeze
All major features for keystone must be reviewed and approved by the end of this week.