c6f2124ae5
There is no reason to impose a short deadline for packaging or lifecycle management projects that want to trail the release. Let's relax the constraints and accept that cycle-trailing releases can happen up to 3 months after the main components synchronized release. Additionally, the idea behind the membership check at milestone-2 is to protect packagers against late additions, not to prevent late-added packaging systems from doing a release. The new rules should also apply to Queens, so that OpenStack-Helm and LOCI can actually do a Queens packaging release, despite having been added post milestone-2. Change-Id: If997e6053af6e74bf6ce8755313346effca6b4e5
11 KiB
Queens Release Schedule
4 September 2017 - 2 March 2018 (26 weeks)
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-5 is on 25 January. Exceptions to this policy will be explicitly mentioned in the event description.
Cross-project events
Queens Goals Research
Pre-cycle planning and investigation into the community-wide goals for Queens.
Queens Project Team Gathering (PTG)
Project team gathering for the Queens cycle 11-15 September 2018 in Denver, Colorado.
Queens-1 milestone
19 October 2017 is the Queens-1 milestone window for projects following the release:cycle-with-milestones model.
Queens Community Goals Acknowledgement
Teams should prepare their acknowledgement of the community-wide goals for.
OpenStack Summit
The OpenStack Summit happens during this week in Sydney, Australia. It will include a "Forum" in which people from all parts of our community will gather to give feedback on the last release (Pike) and discuss requirements for the next development cycle (Rocky).
Queens-2 milestone
7 December 2017 is the Queens-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.
Queens-3 milestone
25 January 2018 is the Queens-3 milestone window for projects following the release:cycle-with-milestones model.
Queens Community Goals Completed
Teams should prepare their documentation for completing the community-wide goals for Queens.
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 Queens-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 Queens-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 5 February 2018 is the target date for projects following the release:cycle-with-milestones model to issue their first release candidate, with a deadline of 8 February 2018.
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 19 February 2018 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).
Queens release
The Queens coordinated release will happen on 28 February 2018.
Queens cycle-trailing release deadline
The release deadline for projects using the release:cycle-trailing model that follow the main release cycle is set to May 30th, 2018.
Newton library releases
Last week for libraries to be released, integrated in upper-constraints to be tested before Newton EOL.
Newton EOL
Newton projects will be EOL'd this week.
Project-specific events
Elections
Election Email Deadline
Contributors that will be in the electorate for the upcoming election should confirm their gerrit email addresses by this date. Electorate rolls are generated after this date and ballots will be sent to the listed gerrit email address.
Rocky PTLs self-nomination
Project team lead candidates for the Rocky cycle should announce their candidacy during this week. Those dates should be confirmed by the Rocky PTL election officials.
Rocky cycle PTLs election
Election week for Project team leads (where an election must be held to determine the winner). Those dates should be confirmed by the Rocky PTL election officials.
Manila
Manila New Driver Submission Deadline
The deadline for submitting new backend drivers to to Manila is 4 Dec 2017 (23:59 UTC). New drivers must be substantially complete, with unit tests, and passing 3rd party CI by this date. Drivers do not need to be merged until the feature freeze date, but drivers that don't meet this deadline will not be considered at all for Queens.
Manila Spec Freeze
All Manila specs must be approved by 19 Oct 2017 (23:59 UTC).
Manila Feature Proposal Freeze
All new Manila features must be proposed and substantially complete, with unit tests by 8 Jan 2018 (23:59 UTC).
Glance
Glance Spec Proposal Freeze
All Glance, python-glanceclient, and glance_store specs must be proposed as patches to the glance-specs repository by 13:00 UTC on Thursday 28 September 2017 (that is, one hour before the weekly Glance meeting begins). While this only allows one week for review and revisions before the Glance Spec Freeze, you can make sure you have extra review time by submitting your patch early.
Glance Spec Freeze
All Glance, python-glanceclient, and glance_store specs must be merged into the glance-specs repository by 23:59 on Friday 6 October 2017. This is a necessary but not sufficient condition for inclusion in the Queens release.
Keystone
Keystone Spec Proposal Freeze
All Keystone specs targeted to Queens must be submitted to the keystone-specs repository by the end of the week.
Keystone Spec Freeze
All Keystone specs targeted to Queens 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.
Cinder
Cinder New Driver Submission Deadline
The deadline for submitting new backend drivers to Cinder is 4 Dec, 2017 (23:59 UTC). New drivers must be complete, with unit tests, passing 3rd party CI and be merged by this date.
Cinder Spec Freeze
All Cinder specs must be approved by 4 Dec, 2017 (23:59 UTC).
Cinder Feature Proposal Freeze
All new Cinder features must be proposed and substantially complete, with unit tests by 19 Jan, 2018 (23:59 UTC).
Sahara
Sahara Plugin Deadline
The deadline for submitting new plugins or plugin versions to Sahara is 8 Dec 2017 (23:59 UTC). The motivation for this deadline is to ensure sufficient time for testing plugins and ensuring their stability. Also, due to the unpredictable release schedule of Hadoop components, we should avoid the practice of delaying plugin upgrades too far into the cycle. Exemptions to this deadline may be granted by the PTL.
Nova
Nova Spec Freeze
All Nova specs must be approved by end of day Thursday October 19th, 2017.