Thierry Carrez 9c41f9b1d0 Fix deep links to governance.o.o

As part of the "neutral governance website" effort, TC-related
governance content is moved under governance.openstack.org/tc.

While those links are preserved through redirects, it doesn't
hurt to give the right examples (and avoid redirection) wherever
we can.

Change-Id: I85160e0c9bdf3d1f3fbf372162415e80dfc41187

2016-12-15 15:47:57 +01:00

5.5 KiB

Raw Blame History

Queens Release Schedule

Note

All deadlines are generally the Thursday of the week on which they are noted above. For example, the Feature Freeze in week XXX is on XXX. Exceptions to this policy will be explicitly mentioned in the event description.

Cross-project events

Queens Goals Research

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

Queens Design Summit

TBD

Queens Project Team Gathering (PTG)

TBD

Queens-1 milestone

XXX is the Queens-1 milestone window for projects following the release:cycle-with-milestones model.

Queens-2 milestone

XXX is the Queens-2 milestone window for projects following the release:cycle-with-milestones model.

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.

Queens-3 milestone

XXX is the Queens-3 milestone window for projects following the release:cycle-with-milestones model.

Extra-ATCs deadline

Project teams should identify contributors who have had a significant impact this cycle but who would not qualify for ATC status using the regular process because they have not submitted a patch. Those names should be added to the governance repo for consideration as ATC for the future.

Although extra ATCs can be nominated at any point, there is a deadline to be included in electorate for the next release cycle. The ATC list needs to be approved by the TC by (TBD), and in order to appear on the TC agenda to be discussed, the proposals need to be submitted to the openstack/governance repository by (TBD).

Feature freeze

The Queens-3 milestone marks feature freeze for projects following the release:cycle-with-milestones model. No featureful patch should be landed after this point. Exceptions may be granted by the project PTL.

Requirements freeze

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

RC1 target week

The week of XXX - XXX is the target date for projects following the release:cycle-with-milestones model to issue their first release candidate, with a deadline of XXX.

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 translator time to finish up their efforts.

Final RCs and intermediary releases

The week of XXX 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).

Queens release

The Queens coordinated release will happen on XXX.

Queens cycle-trailing Deadline

The deadline for projects using the release:cycle-trailing model that follow the main release cycle.

Project-specific events

Elections

R-cycle PTLs self-nomination

Project team lead candidates for the Queens cycle should announce their candidacy during this week.

R-cycle cycle PTLs election

Election week for Project team leads (where an election must be held to determine the winner).

TC member self-nomination

Candidates for the partial Technical Committee member renewal should announce their candidacy during this week.

TC member election

Election for partially renewing Technical Committee members will happen during this week.

5.5 KiB Raw Blame History