On Fri, Jan 24, 2014 at 8:26 AM, Russell Bryant <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01/23/2014 08:31 PM, Michael Basnight wrote: >> >> On Jan 23, 2014, at 5:10 PM, Mark McClain wrote: >> >>> >>> On Jan 23, 2014, at 5:02 PM, Russell Bryant <[email protected]> >>> 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 > > That makes sense. It's worth saying that if we have this deadline, > every PTL should be able to grant exceptions on a case by case basis. > I think things getting finished up in your meetup is a good case for > a set of exceptions. > > - -- > Russell Bryant > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlLihg0ACgkQFg9ft4s9SAYbJwCffD0hFkNvHgl6+S0U4ez4VLKQ > TlkAoIvNzuv3YazKo2Y0cFAnh6WLPWR2 > =k5bu > -----END PGP SIGNATURE----- > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I'm in agreement with trying out coordination of the dates this time around. I am concerned about the date (Feb 18) given the issues we've had with the Gate etc. It feels a bit early at just over three weeks, especially now that we've punted most of our I2 blueprints. I'm on board though, and the 18'th isn't unreasonable. _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
