Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


https://bugs.freedesktop.org/show_bug.cgi?id=79123

--- Comment #8 from Björn Michaelsen <bjoern.michaelsen@canonical.com> ---
(In reply to comment #7)
In any case what is the goal here ? If I mark a patch -2 myself, that means
it is not ready, and it also mean I'm aware of it and will follow up on
it... or abandon it myself if need be. Why would you want to mess with that
? what is the benefit ?

This is to prevent reviewer to run into the same unchanged patches again and
again when checking on janitorial patrol. Frustrating reviewer is not something
we should do as they are rare anyway.

As said trying to get feedback on a self-inflicted -2 change is suboptimal
anyway as a/ there are drafts for that b/ many reviewers will not even open a
change marked as -2 on the overview, esp. when that change is a few weeks old

The auto-abandon stops frustrating those few reviewer that do walk _all_ change
(which is a good thing) and it reminds the submitters that they still have
something open and it hurts the change in no way. As a casual submitter to
openstack, I found the autoabandon very helpful and not at all discouraging --
rather it promotes engagement.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.