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.

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.

Cinder¶

Manila¶

Oslo¶