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

2014-12-01 20:38 GMT+02:00 Rimas Kudelis <>:

It would for example also be possible to have "master" project in
pootle (instead of just for the release-branches), so that the amount
of changes are incremental, and not all one or two months before a new
major release.
(but that of course means applying a translation to multiple projects,
so not sure whether that really reduces the work and not causing more
work for translators...)

For at least a few years, I performed most of my Mozilla localization
work on their master branch. When branches were cut and repositories
migrated, I would migrate my repos too. I can imagine a scenario where
at least some teams would want to work on LibO master as well. There
even is potential that such process could help avoid some problems by
signaling them early enough so that they can be fixed or undone.

Obviously though, this should not be required from all teams. And if we
have at least two simultaneously active release branches, this might not
be the best approach.

I for one -- i.e. the Estonian team :) -- would very much like to work on
master branch.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.