<div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Also, can I recommend that to avoid last minute rush of all the code in Juno-3 (and then clogging up the gate at that time), we work as a team to re-review patches that have addressed all previously identified issues?</div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">For example, the for the GBP plugin, the first series of patches have been updated to address all issues that were identified, and doing re-review/merge now would reduce the load near the end of the cycle.</div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Regards,</div><div class="gmail_default" style="font-size:small">Mandeep</div><div class="gmail_default" style="font-size:small">
-----</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Jul 30, 2014 at 10:52 AM, Kyle Mestery <span dir="ltr"><<a href="mailto:mestery@mestery.com" target="_blank">mestery@mestery.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I wanted to send an email to let everyone know where we're at in the<br>
Juno cycle. We're hitting our stride in Juno-3 development now, and we<br>
have a lot of BPs targeted [1]. Due to this, I'm not going to approve<br>
any more spec exceptions other than possibly flavors [2] and even less<br>
possibly rootwrap [3] if the security implications can be worked out.<br>
The reality is, we're severely oversubscribed as it is, and we won't<br>
land even half of the approved BPs in Juno-3.<br>
<br>
Also, for people with BPs approved for Juno-3, remember Neutron is<br>
observing the Feature Proposal Freeze [4], which is August 21. Any BP<br>
without code proposed by then will be deferred to Kilo.<br>
<br>
As always, the dates for the Juno release can be found on the wiki here [5].<br>
<br>
Thanks!<br>
Kyle<br>
<br>
[1] <a href="https://launchpad.net/neutron/+milestone/juno-3" target="_blank">https://launchpad.net/neutron/+milestone/juno-3</a><br>
[2] <a href="https://review.openstack.org/#/c/102723/" target="_blank">https://review.openstack.org/#/c/102723/</a><br>
[3] <a href="https://review.openstack.org/#/c/93889/" target="_blank">https://review.openstack.org/#/c/93889/</a><br>
[4] <a href="https://wiki.openstack.org/wiki/FeatureProposalFreeze" target="_blank">https://wiki.openstack.org/wiki/FeatureProposalFreeze</a><br>
[5] <a href="https://wiki.openstack.org/wiki/NeutronJunoProjectPlan" target="_blank">https://wiki.openstack.org/wiki/NeutronJunoProjectPlan</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div>