On Wed, Mar 21, 2018 at 2:12 PM, Eric Fried <openst...@fried.cc> wrote:
> +1 for the-earlier-the-better, for the additional reason that, if we > don't finish, we can do another one in time for spec freeze. > > +1 for Wed 27th March. > And I, for one, wouldn't be offended if we could "officially start > development" (i.e. focus on patches, start runways, etc.) before the > mystical but arbitrary spec freeze date. > > Sure, but given we have a lot of specs to review, TBH it'll be possible for me to look at implementation patches only close to the 1st milestone. > On 03/20/2018 07:29 PM, Matt Riedemann wrote: > > On 3/20/2018 6:47 PM, melanie witt wrote: > >> I was thinking that 2-3 weeks ahead of spec freeze would be > >> appropriate, so that would be March 27 (next week) or April 3 if we do > >> it on a Tuesday. > > > > It's spring break here on April 3 so I'll be listening to screaming > > kids, I mean on vacation. Not that my schedule matters, just FYI. > > > > But regardless of that, I think the earlier the better to flush out > > what's already there, since we've already approved quite a few > > blueprints this cycle (32 to so far). > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
