Is common sense an option here? More specifically I mean leveraging the common sense of both contributors and core reviewers (or whoever is authorized to abandon patches).
The formers should abandon patches they're not working on anymore, and expect somebody else to do that if the patches they own end up in a stale condition (where the definition of stale might be relative); the latters should be very considerate in using this function, using it sparingly and always providing justification, perhaps not auto generated. Salvatore On 3 March 2015 at 19:49, Stefano Maffulli <stef...@openstack.org> wrote: > On Tue, 2015-03-03 at 17:10 +0200, Duncan Thomas wrote: > > I feel the need to abandon changes that seem abandoned > > I think there is an agreement that there should be a way to have a clean > view of changesets that are being actively worked on, changes where the > owner is responding to comments, working on it, rebasing as needed, or > waiting for votes/comments. > > For contributors, including the slow ones, I think nobody would object > that it's also good for them to login on https://review.openstack.org/ > and see the list of their changesets, with votes and comments up where > they left them (instead of in the "Recently closed"). > > So I think we go back to tooling: hopefully new version of gerrit will > have a better way to distinguish 'abandoned' from 'inactive'. Until > then, what other options do we have? > > /stef > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
