What would be the best practice for those who realize their work will not make it in Juno? Is it enough to not submit code for review? Would it be better to also request a change in milestone? Thanks, Mohammad From: Kyle Mestery <mestery at mestery.com> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org> Date: 08/12/2014 09:15 AM Subject: [openstack-dev] [neutron] Feature Proposal Freeze is 9 days away Just a reminder that Neutron observes FPF [1], and it's 9 days away. We have an incredible amount of BPs which do not have code submitted yet. My suggestion to those who own one of these BPs would be to think hard about whether or not you can realistically land this code in Juno before jamming things up at the last minute. I hope we as a team can refocus on the remaining Juno tasks for the rest of Juno now and land items of importance to the community at the end. Thanks! Kyle [1] https://wiki.openstack.org/wiki/FeatureProposalFreeze _______________________________________________ OpenStack-dev mailing list OpenStack-dev at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140812/1770ecc5/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140812/1770ecc5/attachment.gif>
