Re: [openstack-dev] [nova] Rocky spec review day
On Wed, 21 Mar 2018 21:48:40 -0700, Melanie Witt wrote: On Tue, 20 Mar 2018 16:47:58 -0700, Melanie Witt wrote: The past several cycles, we've had a spec review day in the cycle where reviewers focus on specs and iterating quickly with spec authors for the day. Spec freeze is April 19 so I wanted to get some input from all of you about what day would work best for a spec review day. 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. Thanks for all who replied on the thread. There was consensus that earlier is better, so let's do the spec review day next week: Tuesday March 27. Thank you to all who participated in the spec review day yesterday. We approved 2 specs, merged some spec amendments, and many other specs received feedback from reviewers. As a reminder, the spec freeze date is at r-2, June 7 this cycle (it has been moved out because of the new review runways effort going on [0]). As we work through the runways queue, we will be looking at approving more specs leading up to r-2, if we make sufficient progress on the queue. Thanks, -melanie [0] https://etherpad.openstack.org/p/nova-runways-rocky __ 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
Re: [openstack-dev] [nova] Rocky spec review day
On Tue, 20 Mar 2018 16:47:58 -0700, Melanie Witt wrote: The past several cycles, we've had a spec review day in the cycle where reviewers focus on specs and iterating quickly with spec authors for the day. Spec freeze is April 19 so I wanted to get some input from all of you about what day would work best for a spec review day. 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. Thanks for all who replied on the thread. There was consensus that earlier is better, so let's do the spec review day next week: Tuesday March 27. Best, -melanie __ 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
Re: [openstack-dev] [nova] Rocky spec review day
On Wed, Mar 21, 2018 at 10:33 PM, Sylvain Bauza wrote: > > > On Wed, Mar 21, 2018 at 2:12 PM, Eric Fried 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. +1 for either one. I think we had enough time to update/push specs after PTG and doing it 2-3 weeks ahead of spec freeze are always helpful. >> > >> > 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 > -gmann __ 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
Re: [openstack-dev] [nova] Rocky spec review day
>> 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. Yeah, I agree. I see runways as an attempt to add pressure to the earlier part of the cycle, where we're ignoring things that have been ready but aren't super high priority because "we have plenty of time." The later part of the cycle is when we start having to make hard decisions on things to de-focus, and where focus on the important core changes goes up naturally anyway. Personally, I think we're already kinda late in the cycle to be going on this, as I would have hoped to exit PTG with a plan to start operating in the new process immediately. Maybe I'm in the minority there, but I think that if we start this process late in the middle of a cycle, we'll probably need to adjust the prioritization of things in the queue more strictly, and remember that when retrospecting on the process for next cycle. > 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. I'm not sure I get this. We can't not review code while we review specs for weeks on end. We've already approved 75% of the blueprints (in number) that we completed in queens. One of the intended outcomes of this effort was to complete a higher percentage of what we approved, so we're not lying to contributors and so we have more focused review of things so they actually get completed instead of half-landed. To that end, I would kind of expect that we need to constantly be throttling (or maybe re-starting) spec review/approval rates to keep the queue full enough so we don't run dry, but without just ending up with a thousand approved things that we'll never get to. Anyway, just MHO. Obviously this will be an experiment and we won't get it right the first time. --Dan __ 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
Re: [openstack-dev] [nova] Rocky spec review day
On Wed, Mar 21, 2018 at 2:12 PM, Eric Fried 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
Re: [openstack-dev] [nova] Rocky spec review day
+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. 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. 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
Re: [openstack-dev] [nova] Rocky spec review day
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). -- Thanks, Matt __ 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-dev] [nova] Rocky spec review day
Hi everybody, The past several cycles, we've had a spec review day in the cycle where reviewers focus on specs and iterating quickly with spec authors for the day. Spec freeze is April 19 so I wanted to get some input from all of you about what day would work best for a spec review day. 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. Please let me know what you think and suggest other days that might work better. Best, -melanie __ 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
