Cinder Release Schedule
After some discussion at the Mitaka Design Summit, the Cinder team will be
altering our release schedule for this release to simplify deadlines and
closer align with the established OpenStack release schedule.
Overall Deadlines for Mitaka [1]
* Mitaka-1 (Dec 1-3)
* Mitaka-2 (Jan 19-21)
* Mitaka-3 (Mar 1-3)
* Final release for client libraries
* FeatureFreeze
* Soft StringFreeze
* Mitaka Release (April 7)
Based on these dates, the following are the deadlines for Cinder changes to be
merged:
* New backend drivers (Jan 19, 7:59 UTC)
* Spec/blueprint approval deadline (Jan 19, 7:59 UTC)
* New features and driver functionality (Mar 1, 7:50 UTC)
* Note: changes that require client updates will need to be
made available in enough time for both client and
service changes to merge.
After the stated deadlines, it will be at the discretion of the Cinder core
team whether to allow any exceptions based on scope of work and perceived risk.
To increase the odds that your code will be accepted in Mitaka - do not wait
until close to the deadlines to submit your work. Code needs to be reviewed
and CI testing performed before it merges. This may take some time. Do not
expect that code submitted prior to the deadline means that it will be
accepted.
Note to new driver submitters:
All requirements stated here [2] and in related pages still apply. Even though
the deadline has been pushed out, all third party CI and code quality
requirements must still be met.
Sean (smcginnis)
[1] https://wiki.openstack.org/wiki/Mitaka_Release_Schedule
[2] https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
