Goutham Pacha Ravi b18360c746 Add Victoria cycle schedule for manila

Change-Id: I234fe19b61618d195eb7fd302665fe494a37465f
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

2020-03-25 15:23:39 -07:00

5.8 KiB

Raw Blame History

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)

Subscribe to iCalendar file

Cross-project events

Victoria Goals Research

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

OpenDev + PTG

The OpenDev+PTG happens during this week in Vancouver, British Columbia. 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).