Xena Release Schedule

Xena 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.

19 April 2021 - 06 October 2021 (25 weeks)

Week

Cross-project events

Project-specific events

Apr 12 - Apr 16

Apr 19 - Apr 23

R-24

Apr 26 - Apr 30

R-23

May 03 - May 07

R-22

May 10 - May 14

R-21

May 17 - May 21

R-20

May 24 - May 28

R-19

May 31 - Jun 04

R-18

Jun 07 - Jun 11

R-17

Jun 14 - Jun 18

R-16

Jun 21 - Jun 25

R-15

Jun 28 - Jul 02

R-14

Jul 05 - Jul 09

R-13

Jul 12 - Jul 16

R-12

Jul 19 - Jul 23

R-11

Jul 26 - Jul 30

R-10

Aug 02 - Aug 06

R-9

Aug 09 - Aug 13

R-8

Aug 16 - Aug 20

R-7

Aug 23 - Aug 27

R-6

Aug 30 - Sep 03

R-5

Sep 06 - Sep 10

R-4

Sep 13 - Sep 17

R-3

Sep 20 - Sep 24

R-2

Sep 27 - Oct 01

R-1

Oct 04 - Oct 08

R-0

Subscribe to iCalendar file

Cross-project events

Xena Goals Research

Pre-cycle planning and investigation into the community-wide goals for Xena.

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.

Xena-1 milestone

27 May, 2021 is the Xena-1 milestone. See project-specific notes for relevant deadlines.

Wallaby Cycle-Trailing Release Deadline

All projects following the cycle-trailing release model must release their Wallaby deliverables by 02 July, 2021.

Xena-2 milestone

15 July, 2021 is the Xena-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 13 August, 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.

Xena-3 milestone

02 September, 2021 is the Xena-3 milestone. See project-specific notes for relevant deadlines.

Feature freeze

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

Xena Community Goals Completed

Teams should prepare their documentation for completing the community-wide goals for Xena.

RC1 target week

The week of 13 September, 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 27 September, 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).

Xena release

The Xena coordinated release will happen on Wednesday, 06 October, 2021.

Open Infrastructure Summit

The Open Infrastructure Summit is expected to take place some time in October. 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. Wallaby Highlights.

Project-specific events

Manila

Manila Spec Freeze

All Manila specs targeted to Xena 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.

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.