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

In the fast-paced world of LibreOffice development, the Jenkins Verified+1 of a Gerrit change's latest patch set may easily have become irrelevant by the time the change is submitted, if there has been sufficient change on the relevant git branch between the patch set's parent and the submit date.
I have filed <https://bugs.chromium.org/p/gerrit/issues/detail?id=13239> "Color-code age of a patch set's parent" as a Gerrit enhancement idea now that might help spot such issues.
As a corollary, when creating a Gerrit change, make sure the change's parent is sufficiently recent to begin with. Pull early, pull often.

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.