Ole,
Auto-abandon is not auto-delete.
Abandoned patches remain accessible in gerrit and the 600+ patches which
would be auto-abandoned would continue to exist in virtually the same
state as they do today. Viewable by all and available to anyone
interested in utilizing them (i.e. restoring, rebasing, retesting).
In my experience, mentally processing auto-abandon is similar to getting
used to someone commenting with '-1' on a patch. It is not meant to be a
rejection of one's submission, but a means of communicating that someone
has suggested an improvement.
If an Auto-abandon notification is viewed as a reminder to rebase one's
patch and re-engage with the community committers, then it can be
welcomed as a positive part of the contribution process and not a
negative rejection of one's work.
Thanks,
-daw-
On 2/1/2021 9:38 AM, otr...@employees.org wrote:
Dave,
To be perfectly honest, other than Andrew's proposal to tweak the auto-abandon
parameters, I have not heard another solution that solves the problem of
cleaning up the current queue and limiting the size of the queue in the future.
Is anyone going to volunteer to manually review/abandon 600+ gerrit changes?
Auto-assigning maintainers to gerrit changes is a separate issue. Please make a
proposal to fix that in its own thread and I will help to get that implemented.
What do you intend to happen with those 600+ abandonded changes in the future?
Assuming there is gold in quite a few of them.
Ole
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18640): https://lists.fd.io/g/vpp-dev/message/18640
Mute This Topic: https://lists.fd.io/mt/80169540/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
