2023.1 Antelope Release Schedule

2023.1 Antelope 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.

05 October 2022 - 22 March 2023 (24 weeks)

Week

Cross-project events

Project-specific events

Oct 03 - Oct 07

Oct 10 - Oct 14

R-23

Oct 17 - Oct 21

R-22

Oct 24 - Oct 28

R-21

Oct 31 - Nov 04

R-20

Nov 07 - Nov 11

R-19

Nov 14 - Nov 18

R-18

Nov 21 - Nov 25

R-17

Nov 28 - Dec 02

R-16

Dec 05 - Dec 09

R-15

Dec 12 - Dec 16

R-14

Dec 19 - Dec 23

R-13

Dec 26 - Dec 30

R-12

Jan 02 - Jan 06

R-11

Jan 09 - Jan 13

R-10

Jan 16 - Jan 20

R-9

Jan 23 - Jan 27

R-8

Jan 30 - Feb 03

R-7

Feb 06 - Feb 10

R-6

Feb 13 - Feb 17

R-5

Feb 20 - Feb 24

R-4

Feb 27 - Mar 03

R-3

Mar 06 - Mar 10

R-2

Mar 13 - Mar 17

R-1

Mar 20 - Mar 24

R+0

Subscribe to iCalendar file

Cross-project events

2023.1 Antelope Project Team Gathering (PTG)

A Virtual PTG will be held during this week (October 17-21, 2022). The Project Teams Gathering provides an opportunity for teams to collaborate and plan, and discuss requirements for future releases.

Antelope-1 milestone

17 November, 2022 is the Antelope-1 milestone. See project-specific notes for relevant deadlines.

Zed Cycle-Trailing Release Deadline

All projects following the cycle-trailing release model must release their Zed deliverables by 14 December, 2022.

Antelope-2 milestone

05 January, 2023 is the Antelope-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 02 February, 2023.

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.

Antelope-3 milestone

16 February, 2023 is the Antelope-3 milestone. See project-specific notes for relevant deadlines.

Feature freeze

The Antelope-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 Antelope-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.

RC1 target week

The week of 27 February, 2023 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 13th - 17th March, 2023 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).

Antelope release

The Antelope coordinated release will happen on Wednesday, 22 March, 2023.

Cycle Highlights

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.

Project-specific events

Cinder

Cinder Mid Cycle PTG - 1

We will be conducting a mid-cycle PTG on 30th November, 2022 (Wednesday) which is a continuation of 2023.1 Antelope PTG to track progress and discuss new topics in a similar manner as of PTG.

Wednesday 30 November 2022 (1400-1600 UTC).

Cinder Spec Freeze

All Cinder Specs for features to be implemented in 2023.1 Antelope must be approved by Friday 16 December 2022 (23:59 UTC).

Cinder New Driver Merge Deadline

The deadline for merging a new backend driver to Cinder for the 2023.1 Antelope release is Friday 20 January 2023 (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. (Note that because of where some holidays fall this cycle, this is later than the usual Milestone-2 deadline.)

Cinder New Target Driver Merge Deadline

The deadline for merging a new target driver to Cinder for the 2023.1 Antelope release is Friday 20 January 2023 (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.

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 10 February 2023.

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 two 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 2023.1 Antelope. (You can look among the Yoga and Zed 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 os-brick 2023.1 Antelope Release

Changes to be included in the 2023.1 Antelope release of the os-brick library must be merged by Thursday 02 February 2023 (20:00 UTC).

Cinder 3rd Party CI Compliance Checkpoint

This is a reminder that in order for a Cinder driver to be considered ‘supported’ in the 2023.1 Antelope 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 Antelope 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.

Manila Hackathon

Manila community event promoted in order to tackle the implementation of features or tech debt areas.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.