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



12.12.2014 u 12:45, Stanislav Horáček je napisao/la:

This workflow means that everyone is forced to work on master - otherwise it is needed to translate the same strings again and again in branches which makes no sense.

And that's why I am confused - because we were assured that it will be possible to choose between working on master and working on branches.



In my head is like this:
- Master is updated every day in pootle, but only source strings. If you translate something, it will stick, but only if dev doesn't change source string again (which is possible since it's work in progress). - When 6 months passes, everything is moved to "stable" branch, including translations.

This is where is gets tricky. How do you transfer translations between master and stable? What if I updated some translations only in stable? Do they get backported to master?

Anyway, as long as they don't delete my translations in stable, I don't have anything against master branch, but I will probably not use it.

Mihovil

--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

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.