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


On Thu, Oct 9, 2014 at 12:00 PM, Andras Timar <timar74@gmail.com> wrote:

On Thu, Oct 9, 2014 at 10:47 AM, Michael Stahl <mstahl@redhat.com> wrote:
The issue is in the decision to backport the first patch without the
configuration option (fdo#81309 only) to 4.3.1 and 4.2.7

It was because of the translation requirement that the backport would
add.

do we really have to make ourselves slaves to un-changeable processes
like "there shall be no new strings in bugfix releases", no matter the
circumstances?

AFAIK there is no policy like "there shall be no new strings in bugfix
releases". The only thing localizers and Pootle maintaners ask, that
such change should be announced to them, so they have a chance to
catch-up.


Can that be done automatically by some script (like in GNOME)?

Simos

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.