Open Stack

That's a very good plan ("Initial feedback/triage") Mike.

thanks,
dims

On Thu, Jul 9, 2015 at 3:23 PM, Mike Scherbakov
<mscherbakov at mirantis.com> wrote:
> +1 for just reusing existing script, and adjust it on the way. No need to
> immediately switch from infinite time to a couple of weeks, we can always
> adjust it later. But 1-2 month should be a good start already.
>
> Our current stats [1] look just terrible. Before we enable an auto-abandon,
> we need to go every single patch first, and review it / provide comment to
> authors. The idea is not to abandon some good patches, and not to offend
> contributors...
>
> Let's think how we can approach it. Should we have core reviewers to check
> their corresponding components?
>
> [1] http://stackalytics.com/report/reviews/fuel-group/open
>
> On Wed, Jul 8, 2015 at 1:13 PM Sean M. Collins <sean at coreitpro.com> wrote:
>>
>> Let's keep it at >4 weeks without comment, and Jenkins failed - similar
>> to the script that Kyle Mestery uses for Neutron. In fact, we could
>> actually just use his script ;)
>>
>>
>> https://github.com/openstack/neutron/blob/master/tools/abandon_old_reviews.sh
>> --
>> Sean M. Collins
>>
>> __________________________________________________________________________
>> 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
>
> --
> Mike Scherbakov
> #mihgen
>
> __________________________________________________________________________
> 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
>



-- 
Davanum Srinivas :: https://twitter.com/dims