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

Hi Hossein,

2011.04.19 16:08, Hossein Noorikhah rašė:
I have to remind that we're in a situation that we only have one
legacy branch. Sooner or later, we will have multiple versions of LibO
strings available on pootle, that not only make the workspace crowded,
but downloading zip folders and operations like this on them, make
pootle slow.
When pootle can't do things in parallel, we can partition the job
logically and put it on multiple servers to gain speed up. So, Why not
setup a pootle instance for legacy strings? All the previous versions
can go there so everyone that needs them can still use it without
switching to a new traslating interface.

Disclaimer: the following is my personal impression.
I don't (yet) think this makes much sense for one simple reason: as far as I remember from OOo, and looking at what we have now, it simply doesn't seem like LibO would be releasing from two or more branches simultaniously often and for long times. Unlike Mozilla. This makes excessive server load from working on old strings quite unlikely in my eyes. I think such load would be more occasional than usual, so in my opinion, it simply doesn't justify maintaining two totally independent installations of Pootle and keeping them in sync with each other.

On the other hand, an upgrade on the current version, keeps everything in place.
Anyway, someday in near future we'll have to remove older versions, so
why not create a guideline for the lifecycle of those old strings and
keep them in a good place?

I think the policy here is quite simple: when there is a decision that there will be no more releases from a certain branch, then that branch should be dropped from Pootle.


Unsubscribe instructions: 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.