Open Stack

Things always move more quickly at the end of a cycle because people feel release pressure, but I do think this is a good idea. 2 - 3 minutes isn’t very realistic. It would need to be planned for longer.





On 9/28/15, 3:57 AM, "Rob Cresswell (rcresswe)" <rcresswe at cisco.com> wrote:

>Hi folks,
>
>I¹m wondering if we could try marking out a small 2-3 minute slot at the
>start of each weekly meeting to highlight Critical/ High bugs that have
>code up for review, as well as important blueprints that have code up for
>review. These would be blueprints for features that were identified as
>high priority at the summit.
>
>The thought here is that we were very efficient in L-RC1 at moving code
>along, which is nice for productivity, but not really great for stability;
>it would be good to do this kind of targeted work earlier in the cycle.
>I¹ve noticed other projects doing this in their meetings, and it seems
>quite effective.
>
>Rob
>
>
>__________________________________________________________________________
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev