Wallaby Release Schedule
Wallaby 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.
Note
All projects following the cycle-trailing release model must release their Wallaby deliverables by 02 July, 2021.
Xena schedule <https://releases.openstack.org/xena/schedule.html>
19 October 2020 - 14 April 2021 (26 weeks)
Week |
Cross-project events |
Project-specific events |
|
|---|---|---|---|
Oct 12 - Oct 16 |
|||
Oct 19 - Oct 23 |
R-25 |
||
Oct 26 - Oct 30 |
R-24 |
||
Nov 02 - Nov 06 |
R-23 |
||
Nov 09 - Nov 13 |
R-22 |
||
Nov 16 - Nov 20 |
R-21 |
||
Nov 23 - Nov 27 |
R-20 |
||
Nov 30 - Dec 04 |
R-19 |
||
Dec 07 - Dec 11 |
R-18 |
||
Dec 14 - Dec 18 |
R-17 |
||
Dec 21 - Dec 25 |
R-16 |
||
Dec 28 - Jan 01 |
R-15 |
||
Jan 04 - Jan 08 |
R-14 |
||
Jan 11 - Jan 15 |
R-13 |
||
Jan 18 - Jan 22 |
R-12 |
||
Jan 25 - Jan 29 |
R-11 |
||
Feb 01 - Feb 05 |
R-10 |
||
Feb 08 - Feb 12 |
R-9 |
||
Feb 15 - Feb 19 |
R-8 |
||
Feb 22 - Feb 26 |
R-7 |
||
Mar 01 - Mar 05 |
R-6 |
||
Mar 08 - Mar 12 |
R-5 |
||
Mar 15 - Mar 19 |
R-4 |
||
Mar 22 - Mar 26 |
R-3 |
||
Mar 29 - Apr 02 |
R-2 |
||
Apr 05 - Apr 09 |
R-1 |
||
Apr 12 - Apr 16 |
R-0 |
Cross-project events¶
Wallaby Goals Research¶
Pre-cycle planning and investigation into the community-wide goals for Wallaby.
Virtual PTG¶
A virtual PTG will be held during this week. The Project Teams Gathering provides and opportunity for teams to collaborate and plan, and discuss requirements for future releases.
Wallaby-1 milestone¶
3 December, 2020 is the Wallaby-1 milestone. See project-specific notes for relevant deadlines.
Victoria Cycle-Trailing Release Deadline¶
All projects following the cycle-trailing release model must release their Victoria deliverables by 14 January, 2021.
Wallaby-2 milestone¶
21 January, 2021 is the Wallaby-2 milestone. See project-specific notes for relevant deadlines.
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.
Extra-ATC freeze¶
All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. That allow teams to list active contributors to their projects and who do not have a code contribution this cycle, and therefore won’t automatically be considered an Active Technical Contributor and allowed to vote. This is done by adding extra-atcs to https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml before the Extra-ATC freeze on 25 February, 2021.
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.
Wallaby-3 milestone¶
11 March, 2021 is the Wallaby-3 milestone. See project-specific notes for relevant deadlines.
Feature freeze¶
The Wallaby-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.
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).
Requirements freeze¶
After the Wallaby-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.
Wallaby Community Goals Completed¶
Teams should prepare their documentation for completing the community-wide goals for Wallaby.
RC1 target week¶
The week of 22 March, 2021 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 5 April, 2021 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).
Wallaby release¶
The Wallaby coordinated release will happen on Wednesday, 14 April, 2021.
Open Infrastructure Summit¶
The Open Infrastructure Summit is expected to take place some time in May. Exact event dates are yet to be determined.
Cycle Highlights¶
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.
For examples of previous release highlights: Stein Highlights, Train Highlights, Ussuri Highlights, Victoria Highlights.
Project-specific events¶
Cinder¶
Cinder Spec Freeze¶
All Cinder Specs for features to be implemented in Wallaby must be approved by Friday 18 December 2020 (23:59 UTC).
Cinder New Driver Merge Deadline¶
The deadline for merging a new backend driver to Cinder for the Wallaby release is Thursday 21 January 2021 (20:00 UTC). New drivers must be (a) code complete including unit tests, (b) merged into the code repository, and (c) must have a 3rd Party CI running reliably. (The idea is that new drivers will be included in a release at the second milestone and thus be easily available for downstream testing, documentation feedback, etc.)
Cinder New Target Driver Merge Deadline¶
The deadline for merging a new target driver to Cinder for the Wallaby release is Thursday 21 January 2021 (20:00 UTC). New target drivers must be (a) code complete including unit tests, (b) merged into the code repository, and (c) must have a 3rd Party CI running reliably. (The idea is that new drivers will be included in a release at the second milestone and thus be easily available for downstream testing, documentation feedback, etc.)
Cinder New Feature Status Checkpoint¶
If your new Cinder feature requires client support, keep in mind that the final release for client libraries is in four weeks. Thus your Cinder feature should be substantially complete with unit tests by this time so that any client changes can be reviewed, tested, and merged before 11 March 2021.
Cinder Driver Features Declaration¶
New features added to Cinder drivers must be merged at the time of the OpenStack-wide Feature Freeze, which is coming up in three weeks. Before the Cinder meeting this week, you should post a blueprint in Launchpad listing the Gerrit reviews of features you’d like to land in Wallaby. (You can look among the Ussuri and Victoria blueprints for examples; contact the PTL if you have any questions.) This will help the team prioritize reviews and give you candid early feedback on whether the features look ready.
Cinder 3rd Party CI Compliance Checkpoint¶
This is a reminder that in order for a Cinder driver to be considered ‘supported’ in the Wallaby release, its third party CI must be running properly when the Cinder team does a final compliance check around the time of the third milestone. See the Driver Compliance section of the Cinder Documentation for details.
Manila¶
Manila Spec Freeze¶
All Manila specs targeted to Wallaby must be approved by the end of the week.
Manila New 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, functional and integration tests by the end of the week.
Oslo¶
Oslo Feature Freeze¶
All new Oslo features must be proposed and substantially complete, with unit tests by the end of the week.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.