On 14/06/13 16:11, Bjoern Michaelsen wrote:
Im not too happy with essentially shutting down all development on master on
one application for an undefined timeframe. Can we make this a bit more
bearable by:
Bjoern, just read it again. He is asking not to merge changes like
german comments or the wholesale string/sal_Bool changes that are low
priority but complicate life when one tries to rebase changes. He also
did not speak about indefinite. Kohei is know to be a fast and concise
fellow, so don't worry, it will not take the same time as chart2.
He just implores the clemency of the pears to make his re-factoring less
of PITA.
F.
a/ a concrete timeframe, I would suggest until the 2013-06-30
(with the option to extend the block another week a few days before the end
should the need arise)
b/ make that work trackable and visible on a regularly pushed branch (maybe
even regularly rebased), so it easier to see where possible conflicts arise
c/ instead of suggesting to stop all work on calc, divert those changes to
gerrit, were those could stay "on hold" until the refactoring is done, and
be merged in due time afterwards ...
Note also that some string refactorings or friends are global (e.g. removing a
member function), and excluding these would block all of LO, which is obviously
not a good thing.
Best,
Bjoern
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
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.