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.
April 3, 2024 - October 2, 2024 (26 weeks)
Week |
Cross-project events |
Project-specific events |
|
---|---|---|---|
Apr 01 - Apr 05 |
|||
Apr 08 - Apr 12 |
R-25 |
||
Apr 15 - Apr 19 |
R-24 |
||
Apr 22 - Apr 26 |
R-23 |
||
Apr 29 - May 03 |
R-22 |
||
May 06 - May 10 |
R-21 |
||
May 13 - May 17 |
R-20 |
||
May 20 - May 24 |
R-19 |
||
May 27 - May 31 |
R-18 |
||
Jun 03 - Jun 07 |
R-17 |
||
Jun 10 - Jun 14 |
R-16 |
||
Jun 17 - Jun 21 |
R-15 |
||
Jun 24 - Jun 28 |
R-14 |
||
Jul 01 - Jul 05 |
R-13 |
||
Jul 08 - Jul 12 |
R-12 |
||
Jul 15 - Jul 19 |
R-11 |
||
Jul 22 - Jul 26 |
R-10 |
||
Jul 29 - Aug 02 |
R-9 |
||
Aug 05 - Aug 09 |
R-8 |
||
Aug 12 - Aug 16 |
R-7 |
||
Aug 19 - Aug 23 |
R-6 |
||
Aug 26 - Aug 30 |
R-5 |
||
Sep 02 - Sep 06 |
R-4 |
||
Sep 09 - Sep 13 |
R-3 |
||
Sep 16 - Sep 20 |
R-2 |
||
Sep 23 - Sep 27 |
R-1 |
||
Sep 30 - Oct 04 |
R+0 |
From April 8 to April 12 we’ll have a virtual PTG to plan the Dalmatian release schedule.
May 16, 2024 is the Dalmatian-1 milestone. See project-specific notes for relevant deadlines.
All projects following the cycle-trailing release model must release their 2024.1 Caracal deliverables by June 6, 2024.
July 4, 2024 is the Dalmatian-2 milestone. See project-specific notes for relevant deadlines.
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.
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 Contributor and allowed to vote. This is done by adding extra-acs to https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml before the Extra-AC freeze date.
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.
August 29, 2024 is the Dalmatian-3 milestone. See project-specific notes for relevant deadlines.
The Dalmatian-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.
Client libraries should issue their final release during this week, to match feature freeze.
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).
After the Dalmatian-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.
The week of September 9, 2024 is the target date for projects following the release:cycle-with-rc model to issue their first release candidate.
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.
The week of September 23, 2024 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).
The Dalmatian coordinated release will happen on Wednesday, October 2, 2024.
Cycle highlights need to be added to the release deliverables after the 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, Wallaby Highlights, Xena Highlights, Yoga Highlights, Zed Highlights. 2023.1 Antelope Highlights. 2023.2 Bobcat Highlights. 2024.1 Caracal Highlights.
All Manila specs targeted to 2024.2 Dalmatian must be approved by the end of the week.
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.
All new Manila features must be proposed and substantially completed, with unit, functional and integration tests by the end of the week. Collaborative review sessions must be proposed at this timeline, in order to speed up the review process.
Manila community event promoted in order to fast-track the closure of bugs.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.