Re: [eclipse-pmc] Review of mass changes

[Mickael Istria <mistria@xxxxxxxxxx>]

On Tue, Jun 25, 2019 at 10:39 AM Stephan Herrmann <stephan.herrmann@xxxxxxxxx> wrote:

With one build taking around 1 hour (please don't complain, this is 1 hour spent
well on lots of tests), each build potentially slows down productive
development. Haven floods of up-to ten cleanup builds is not nice.

Please don't assume that cleanup is not productive. Tackling technical debt helps software to run better, to be more readable, more maintainable and more accessible to newcomers, ultimately facilitating "capture" of more human resources investing in the project.

However, if you're working on a high priority change and feel really stuck by the Gerrit queue, you can stop the other running Gerrit jobs from Jenkins until yours. When doing so, it would be nice to add a message on Gerrit: "we aborted the build because we currently need more immediate feedback on some other change, a new build will be retriggered when you publish a new patch set, or feel free to ping if you need it retriggered later."