20 February 2017 - 1 September 2017 (27 weeks)
|Week||Cross-project events||Project-specific events|
|Feb 20 - Feb 24|
|Feb 27 - Mar 03||R-26|
|Mar 06 - Mar 10||R-25|
|Mar 13 - Mar 17||R-24|
|Mar 20 - Mar 24||R-23|
|Mar 27 - Mar 31||R-22|
|Apr 03 - Apr 07||R-21|
|Apr 10 - Apr 14||R-20|
|Apr 17 - Apr 21||R-19|
|Apr 24 - Apr 28||R-18|
|May 01 - May 05||R-17|
|May 08 - May 12||R-16|
|May 15 - May 19||R-15|
|May 22 - May 26||R-14|
|May 29 - Jun 02||R-13|
|Jun 05 - Jun 09||R-12|
|Jun 12 - Jun 16||R-11|
|Jun 19 - Jun 23||R-10|
|Jun 26 - Jun 30||R-9|
|Jul 03 - Jul 07||R-8|
|Jul 10 - Jul 14||R-7|
|Jul 17 - Jul 21||R-6|
|Jul 24 - Jul 28||R-5|
|Jul 31 - Aug 04||R-4|
|Aug 07 - Aug 11||R-3|
|Aug 14 - Aug 18||R-2|
|Aug 21 - Aug 25||R-1|
|Aug 28 - Sep 01||R+0|
|Sep 04 - Sep 08||R+1|
|Sep 11 - Sep 15||R+2|
With the exception of the final release date and cycle-trailing release date, deadlines are generally the Thursday of the week on which they are noted above. For example, the Feature Freeze in week R-5 is on 27 July. Exceptions to this policy will be explicitly mentioned in the event description.
Project team gathering for the Pike release 20-24 February 2017 in Atlanta, Georgia.
XXX is the Pike-1 milestone window for projects following the release:cycle-with-milestones model.
Teams should prepare their acknowledgement of the community-wide goals for Pike.
The OpenStack Summit happens during this week in Boston, USA. It will include a “Forum” in which people from all parts of our community will gather to give feedback on the last release (Ocata) and discuss requirements for the next development cycle (Queens).
XXX is the Pike-2 milestone window for projects following the release:cycle-with-milestones model.
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.
XXX is the Pike-3 milestone window for projects following the release:cycle-with-milestones model.
Teams should prepare their documentation for completing the community-wide goals for Pike.
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).
The Pike-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.
After the Pike-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.
Client libraries should issue their final release during this week, to match feature freeze.
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).
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.
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.
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.
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).
The Pike coordinated release will happen on XXX.
The deadline for projects using the release:cycle-trailing model that follow the main release cycle.