Newton release schedule

Newton release schedule

Week Cross-project events Project-specific events
Apr 04-08   Mitaka release  
Apr 11-15 R-25    
Apr 18-22 R-24    
Apr 25-29 R-23 Newton Design Summit  
May 02-06 R-22    
May 09-13 R-21    
May 16-20 R-20    
May 23-27 R-19    
May 30-03 R-18 newton-1 milestone Nova non-priority spec approval freeze
  Keystone Spec Proposal Freeze
Jun 06-10 R-17    
Jun 13-17 R-16   Trove Spec Proposal Deadline
Jun 20-24 R-15    
Jun 27-01 R-14   Nova non-priority feature freeze
Jul 04-08 R-13   Keystone Spec Freeze
Jul 11-15 R-12 newton-2 milestone Cinder New Backend Driver Deadline
Membership Freeze Cinder Spec Freeze
  Trove Spec Freeze
  Keystone Feature Proposal Freeze
Jul 18-22 R-11    
Jul 25-29 R-10    
Aug 01-05 R-9   Nova priority spec approval freeze
Aug 08-12 R-8 extra-atcs deadline  
Aug 15-19 R-7    
Aug 22-26 R-6 Final release for non-client libraries Trove Client Soft Freeze
  Trove Guest Requirements Freeze:
  Horizon Feature Freeze
Aug 29-02 R-5 newton-3 milestone Cinder Feature Freeze
Feature freeze Trove Feature Freeze
Final release for client libraries Keystone Feature Freeze
Soft StringFreeze  
Requirements freeze  
Sep 05-09 R-4    
Sep 12-16 R-3 RC1 target week Ocata cycle PTLs self-nomination
Hard StringFreeze  
Sep 19-23 R-2   Ocata cycle PTLs election
Sep 26-30 R-1 Final RCs and intermediary releases TC member self-nomination
Oct 03-07 R+0 Newton release TC member election
Oct 10-14 R+1    
Oct 17-21 R+2 Newton cycle-trailing Deadline  
Oct 24-28 R+3 Ocata Design Summit  

Note

All 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 1 September. Exceptions to this policy will be explicitly mentioned in the event description.

Cross-project events

Newton Design Summit

Planning in Austin

newton-1 milestone

May 31 - June 2 is the newton-1 milestone window for projects following the release:cycle-with-milestones model.

newton-2 milestone

July 12-14 is the newton-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.

newton-3 milestone

August 30 - Sept 1 is the newton-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 25 Aug, and in order to appear on the TC agenda to be discussed, the proposals need to be submitted to the openstack/governance repository by 16 Aug.

Feature freeze

The newton-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 newton-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 September 12 is the target date for projects following the release:cycle-with-milestones 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 translator time to finish up their efforts.

Final RCs and intermediary releases

The week of September 26 is the last week to issue release candidates or intermediary releases before release week. On release week only final-release-critical releases will be accepted (at the discretion of the release team).

Newton release

The Newton coordinated release will happen on October 6th, 2016.

Newton cycle-trailing Deadline

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

Project-specific events

Elections

Ocata cycle PTLs self-nomination

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

Ocata 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.

Cinder

Cinder New Backend Driver Deadline

The deadline for getting a new backend driver added to Cinder is 12th July, 2016. All review issues must be addressed and third party CI must be reporting and stable with enough time for reviewers prior to the deadline. Meeting these requirements on the 12th does not guarantee core reviewers will have enough time to merge the driver.

Cinder Spec Freeze

All Cinder specs must be approved by 12th July, 2016.

Cinder Feature Freeze

The deadline for new features and driver functionality is 31 August, 2016. Any changes past that date will be at the discretion of the core team.

Nova

For reference, these are the Nova review priorities for Newton.

Nova non-priority spec approval freeze

All non-priority Nova specs must be approved by June 2nd, 2016.

Nova non-priority feature freeze

The deadline for non-priority features is June 30th, 2016. There may be a round of feature freeze exceptions but that will be at the discretion of the Nova core team.

Nova priority spec approval freeze

All priority Nova specs must be approved by August 4th, 2016. This is intentionally after the Nova midcycle meetup for Newton so there is some time for last minute adjustments to priority features.

Trove

The deadlines below are specific to the Trove project.

Trove Spec Proposal Deadline

Submit all Trove specs for the Newton release by the end of this week (for review) in trove-specs repository.

Trove Spec Freeze

All Trove specs for the Newton release must be approved by the end of this week.

Trove Guest Requirements Freeze:

Freeze the requirements for all guest agents by this date and make the newton requirements file for guests.

Trove Client Soft Freeze

All major features for the python-troveclient must be reviewed and approved by the end of this week, this gives us one additional week to address any issues with dependencies.

Trove Feature Freeze

All major Trove features and projects for Newton must be approved by the end of this week.

This is the deadline for the Trove server, the python-troveclient and all trove-dashboard changes.

Horizon

The deadlines below are specific to the Horizon project.

Horizon Feature Freeze

The deadline for Horizon features for Newton. This is a week earlier than the standard milestone to allow plugins time to sync before the standard release.

Keystone

Keystone Spec Proposal Freeze

The deadline for proposing a Keystone specification that will land in the Newton development cycle.

Keystone Spec Freeze

The deadline for merging a Keystone Spec and approving a blueprint.

Keystone Feature Proposal Freeze

The deadline for proposing code for an approved feature. The code must: show functionality and be ready for review. Approved features that miss the deadline will be moved to the backlog or the first milestone of the next release.

Keystone Feature Freeze

All approved features must be merged by this week. Please note, the Keystone Feature Freeze date is aligned with Feature freeze.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.