[openstack-dev] [Fuel] Abandon changesets which hang for a while without updates

Oleg Gelbukh ogelbukh at mirantis.com
Wed Jul 8 11:33:53 UTC 2015

Given this is _inactivity_ timeout, 2 weeks seem more than enough. Mind
that the discussion without any patch sets incoming counts against this
limit as well.

And basically, if you go on a lenghty vacation, you better finish with all
your CRs before that. During that time it's likely that changes will
require manual rebase anyways, so no point to keep them in listings and
search results.

So I'm for 2 weeks auto-abandon period.

Best regards,
Oleg Gelbukh

On Tue, Jul 7, 2015 at 11:34 PM, Mike Scherbakov <mscherbakov at mirantis.com>

> Hi,
> we have too many patches which hang for over a month without attention.
> Almost all are those which should be abandoned due to changes happened in
> master, and need complete rework. Or, those were just proposals to make
> something, which didn't fly. Unfortunately there are those which were good
> ideas, but didn't attract enough attention from cores and didn't land into
> master as a result.
> Anyway, I think we need to keep our review queues in better health. Can we
> enable auto-abandon back again, if patch is hanging out for a month or more?
> --
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150708/31f01fe1/attachment.html>

More information about the OpenStack-dev mailing list