<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Autoabandon gerrit changes with negative feedback and more than 1 month without action" href="https://bugs.freedesktop.org/show_bug.cgi?id=79123#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Autoabandon gerrit changes with negative feedback and more than 1 month without action" href="https://bugs.freedesktop.org/show_bug.cgi?id=79123">bug 79123</a> from <a class="email" href="mailto:bjoern.michaelsen@canonical.com" title="Björn Michaelsen <bjoern.michaelsen@canonical.com>"> Björn Michaelsen</a> <pre>(In reply to <a href="show_bug.cgi?id=79123#c7">comment #7</a>) > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>