Victoria Release Schedule

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

18 May 2020 - 16 October 2020 (22 weeks)

Week

Cross-project events

Project-specific events

May 11 - May 15

May 18 - May 22

R-21

May 25 - May 29

R-20

Jun 01 - Jun 05

R-19

Jun 08 - Jun 12

R-18

Jun 15 - Jun 19

R-17

Jun 22 - Jun 26

R-16

Jun 29 - Jul 03

R-15

Jul 06 - Jul 10

R-14

Jul 13 - Jul 17

R-13

Jul 20 - Jul 24

R-12

Jul 27 - Jul 31

R-11

Aug 03 - Aug 07

R-10

Aug 10 - Aug 14

R-9

Aug 17 - Aug 21

R-8

Aug 24 - Aug 28

R-7

Aug 31 - Sep 04

R-6

Sep 07 - Sep 11

R-5

Sep 14 - Sep 18

R-4

Sep 21 - Sep 25

R-3

Sep 28 - Oct 02

R-2

Oct 05 - Oct 09

R-1

Oct 12 - Oct 16

R-0

Oct 19 - Oct 23

R+1

Subscribe to iCalendar file

Cross-project events

Victoria Goals Research

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

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.

Victoria-1 milestone

18 June, 2020 is the Victoria-1 milestone. See project-specific notes for relevant deadlines.

Ussuri Cycle-Trailing Release Deadline

All projects following the cycle-trailing release model must release their Ussuri deliverables by 13 August, 2020.

Victoria-2 milestone

30 July, 2020 is the Victoria-2 milestone. See project-specific notes for relevant deadlines.

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.

Victoria-3 milestone

10 September, 2020 is the Victoria-3 milestone. See project-specific notes for relevant deadlines.

Victoria Community Goals Completed

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

Feature freeze

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

Requirements freeze

After the Victoria-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.

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

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.

RC1 target week

The week of 21 September 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 October 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).

Victoria release

The Victoria coordinated release will happen on Wednesday, 14 October, 2020.

Open Infrastructure Summit

The virtual Open Infrastructure Summit will take place October 19-23.

Project-specific events

Cinder

Cinder Spec Freeze

All Cinder Specs for features to be implemented in Victoria must be approved by Wednesday 1 July 2020 (23:59 UTC).

Cinder New Driver Merge Deadline

The deadline for merging a new backend driver to Cinder for the Victoria release is Thursday 30 July 2020 (23:59 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 Victoria release is Thursday 30 July 2020 (23:59 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 three 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 September. Keep in mind that 7 September is a holiday for many Cinder core reviewers, so we will have reduced bandwith around the time of the Feature Freeze. So please plan ahead.

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. During this week, you should post a blueprint in Launchpad listing the Gerrit reviews of features you’d like to land in Victoria. (You can look among the Ussuri 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. Due to the 7 September holiday in the USA, there will be reduced reviewing bandwidth right around the Feature Freeze, so it will pay to plan ahead.

Cinder 3rd Party CI Compliance Checkpoint

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