On Tue, May 22, 2012 at 12:27 AM, David Tardon <dtardon@redhat.com> wrote:
Yes, and I plan to do that for the three of my branches. But
feature/gbuild_testtools is not a big change, compared to the others, is
based on pretty recent master (testtools does not change much anyway),
so I would allow it to go directly to master. But I will listen to
counterarguments, e.g., it is possible people (especially those not
using Linux/x86_64) do not have the time or processing power to test
more than one branch. That would be a good reason for merging all the
pending conversions onto one branch.
That was my angle indeed... especially for windows were any
out-of-band testing is a multiple hours operation, that do require so
manual attention.
So, as much as I want to test it _before_ we get to master, doing it
for 5 or 6 individual branch is a bit much
Norbert.
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.