On Jan 23, 2014, at 5:10 PM, Mark McClain wrote: > > On Jan 23, 2014, at 5:02 PM, Russell Bryant <rbry...@redhat.com> wrote: > >> Greetings, >> >> Last cycle we had A "feature proposal deadline" across some projects. >> This was the date that code associated with blueprints had to be posted >> for review to make the release. This was in advance of the official >> feature freeze (merge deadline). >> >> Last time this deadline was used by 5 projects across 3 different dates [1]. >> >> I would like to add a deadline for this again for Nova. I'm thinking 2 >> weeks ahead of the feature freeze right now, which would be February 18th. >> >> I'm wondering if it's worth coordinating on this so the schedule is less >> confusing. Thoughts on picking a single date? How's Feb 18? > > I like the idea of selecting a single date. Feb 18th fits with the timeline > the Neutron team has used in the past.
So, Feb 19~21 is the trove mid cycle sprint, which means we might push last minute finishing touches on things during those 3 days. Id prefer the next week of feb if at all possible. Otherwise im ok w/ FFE's and such if im in the minority, because i do think a single date would be best for everyone. So, +0 from trove. :D
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
