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.
October 5, 2023 - April 3, 2024 (26 weeks)
Week |
Cross-project events |
Project-specific events |
|
---|---|---|---|
Oct 02 - Oct 06 |
|||
Oct 09 - Oct 13 |
R-25 |
||
Oct 16 - Oct 20 |
R-24 |
||
Oct 23 - Oct 27 |
R-23 |
||
Oct 30 - Nov 03 |
R-22 |
||
Nov 06 - Nov 10 |
R-21 |
||
Nov 13 - Nov 17 |
R-20 |
||
Nov 20 - Nov 24 |
R-19 |
||
Nov 27 - Dec 01 |
R-18 |
||
Dec 04 - Dec 08 |
R-17 |
||
Dec 11 - Dec 15 |
R-16 |
||
Dec 18 - Dec 22 |
R-15 |
||
Dec 25 - Dec 29 |
R-14 |
||
Jan 01 - Jan 05 |
R-13 |
||
Jan 08 - Jan 12 |
R-12 |
||
Jan 15 - Jan 19 |
R-11 |
||
Jan 22 - Jan 26 |
R-10 |
||
Jan 29 - Feb 02 |
R-9 |
||
Feb 05 - Feb 09 |
R-8 |
||
Feb 12 - Feb 16 |
R-7 |
||
Feb 19 - Feb 23 |
R-6 |
||
Feb 26 - Mar 01 |
R-5 |
||
Mar 04 - Mar 08 |
R-4 |
||
Mar 11 - Mar 15 |
R-3 |
||
Mar 18 - Mar 22 |
R-2 |
||
Mar 25 - Mar 29 |
R-1 |
||
Apr 01 - Apr 05 |
R+0 |
From October 23 to October 27 we’ll have a virtual PTG to plan the Caracal release schedule.
November 16, 2023 is the Caracal-1 milestone. See project-specific notes for relevant deadlines.
All projects following the cycle-trailing release model must release their Bobcat deliverables by 7 December, 2023.
January 11, 2024 is the Caracal-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 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 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.
February 29, 2024 is the Caracal-3 milestone. See project-specific notes for relevant deadlines.
The Caracal-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 Caracal-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 March 11, 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 March 25, 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 Caracal coordinated release will happen on Wednesday, April 3, 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.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.