On Mon, Jul 16, 2012 at 07:19:08PM +0400, Ivan Timofeev wrote:
It is inconsistent, I mean if master is free-pushable (the only
requirement is: no build breaks), it must remain so, regardless of
the workflow a whimmy developer decided to use at the moment.
Right. Im getting more and more convinced, we should simply put solve that with
generate-new-ChangeId-on-release-cherrypick, which will be done by our tooling.
Best,
Bjoern
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.