Cheng
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Tuesday, 29 September 2015 04:11
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.op
st (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Horizon] Horizon Productivity Suggestion
I agree with Travis that 2-3 minutes is not enough, that may not be even enough
to talk about one bug. :)
We could save some time if we have someone monito
I agree with Travis that 2-3 minutes is not enough, that may not be even
enough to talk about one bug. :)
We could save some time if we have someone monitoring the bugs/feature and
publish the high priority item into a report - something similar to what
Keystone does [1]. Reviewers can look this
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)" wrote:
>Hi folks,
>
>I¹m wondering if
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 a