[openstack-dev] [TripleO] Set WIP for stale patches?

Derek Higgins derekh at redhat.com
Wed Sep 17 13:48:40 UTC 2014


On 17/09/14 14:40, Charles Crouch wrote:
> 
> 
> ----- Original Message -----
>> Hi,
>>
>> as part of general housekeeping on our reviews, it was discussed at last
>> week's meeting [1] that we should set workflow -1 for stale reviews
>> (like gerrit used to do when I were a lad).
>>
>> The specific criteria discussed was 'items that have a -1 from a core
>> but no response from author for 14 days'. This topic came up again
>> during today's meeting and it wasn't clear if the intention was for
>> cores to start enforcing this? So:
>>
>> Do we start setting WIP/workflow -1 for those reviews that have a -1
>> from a core but no response from author for 14 days
>>
>> thanks, marios
>>
>> [1]
>> http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-09-09-19.04.log.html
> 
> So it looks like this has already started..
> 
> https://review.openstack.org/#/c/105275/
> 
> I think we need to document on the wiki *precisely* the criteria for setting 
> WIP/workflow -1.
Yup, we definitely should

> For example that review above has a Jenkins failure but no
> core reviews at all.
FWIW I reckon a jenkins -1 should also start the 2 week clock but in the
case you've linked the -1 was only 2 days ago so should have remained
untouched.

> 
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 




More information about the OpenStack-dev mailing list