<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 2, 2015 at 7:27 PM, Sean McGinnis <span dir="ltr"><<a href="mailto:sean.mcginnis@gmx.com" target="_blank">sean.mcginnis@gmx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Cinder Release Schedule<br>
<br>
After some discussion at the Mitaka Design Summit, the Cinder team will be<br>
altering our release schedule for this release to simplify deadlines and<br>
closer align with the established OpenStack release schedule.<br>
<br>
Overall Deadlines for Mitaka [1]<br>
<br>
* Mitaka-1 (Dec 1-3)<br>
* Mitaka-2 (Jan 19-21)<br>
* Mitaka-3 (Mar 1-3)<br>
* Final release for client libraries<br>
* FeatureFreeze<br>
* Soft StringFreeze<br>
* Mitaka Release (April 7)<br>
<br>
<br>
Based on these dates, the following are the deadlines for Cinder changes to be<br>
merged:<br>
<br>
* New backend drivers (Jan 19, 7:59 UTC)<br>
* Spec/blueprint approval deadline (Jan 19, 7:59 UTC)<br>
* New features and driver functionality (Mar 1, 7:50 UTC)<br>
* Note: changes that require client updates will need to be<br>
made available in enough time for both client and<br>
service changes to merge.<br>
<br>
After the stated deadlines, it will be at the discretion of the Cinder core<br>
team whether to allow any exceptions based on scope of work and perceived risk.<br>
<br>
To increase the odds that your code will be accepted in Mitaka - do not wait<br>
until close to the deadlines to submit your work. Code needs to be reviewed<br>
and CI testing performed before it merges. This may take some time. Do not<br>
expect that code submitted prior to the deadline means that it will be<br>
accepted.<br>
<br>
Note to new driver submitters:<br>
All requirements stated here [2] and in related pages still apply. Even though<br>
the deadline has been pushed out, all third party CI and code quality<br>
requirements must still be met.<br>
<br>
Sean (smcginnis)<br>
<br>
[1] <a href="https://wiki.openstack.org/wiki/Mitaka_Release_Schedule" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Mitaka_Release_Schedule</a><br>
[2] <a href="https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div><div class="gmail_extra"><div class="gmail_default" style="font-family:monospace,monospace">Seems reasonable to me, and a descent balance of process/deadlines without going overboard.</div><br></div></div>