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?
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. Regards, Mandeep ----- On Wed, Jul 30, 2014 at 10:52 AM, Kyle Mestery <mest...@mestery.com> wrote: > I wanted to send an email to let everyone know where we're at in the > Juno cycle. We're hitting our stride in Juno-3 development now, and we > have a lot of BPs targeted [1]. Due to this, I'm not going to approve > any more spec exceptions other than possibly flavors [2] and even less > possibly rootwrap [3] if the security implications can be worked out. > The reality is, we're severely oversubscribed as it is, and we won't > land even half of the approved BPs in Juno-3. > > Also, for people with BPs approved for Juno-3, remember Neutron is > observing the Feature Proposal Freeze [4], which is August 21. Any BP > without code proposed by then will be deferred to Kilo. > > As always, the dates for the Juno release can be found on the wiki here > [5]. > > Thanks! > Kyle > > [1] https://launchpad.net/neutron/+milestone/juno-3 > [2] https://review.openstack.org/#/c/102723/ > [3] https://review.openstack.org/#/c/93889/ > [4] https://wiki.openstack.org/wiki/FeatureProposalFreeze > [5] https://wiki.openstack.org/wiki/NeutronJunoProjectPlan > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
