aa70e7d786
This is a proposed schedule for the Train release. Change-Id: Id2b50afa05a2b94da9d92520ba7f49a153973276 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
5.4 KiB
Train Release Schedule
15 April 2019 - 16 October 2019 (27 weeks)
Note
Deadlines are generally the Thursday of the week on which they are noted above. Exceptions to this policy will be explicitly mentioned in the event description.
Cross-project events
Train Goals Research
Pre-cycle planning and investigation into the community-wide goals for Train.
Train-1 milestone
6 June, 2019 is the Train-1 milestone. See project-specific notes for relevant deadlines.
Train Community Goals Acknowledgement
Teams should prepare their acknowledgement of the community-wide goals for.
Open Infrastructure Summit
The Open Infrastructure Summit happens during this week in Shanghai, China. It will include a "Forum" in which people from all parts of our community will gather to give feedback on the last release (Stein) and discuss requirements for the next development cycle (U).
Train-2 milestone
25 July, 2019 is the Train-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.
Train-3 milestone
12 September, 2019 is the Train-3 milestone. See project-specific notes for relevant deadlines.
Train Community Goals Completed
Teams should prepare their documentation for completing the community-wide goals for Train.
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.
Feature freeze
The Train-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 Train-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 September 23-27 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 October 7-11 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).
Train release
The Train coordinated release will happen on 16 October 2019.
Train cycle-trailing release deadline
The release deadline for projects using the release:cycle-trailing model that follow the main release cycle is set to 17 December, 2019.