Hi,
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.
Migeration would also be easy. MySQL tables and files are copied to
the server that holds legacy files.
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?
Hossein
On 4/19/11, Andras Timar <timar74@gmail.com> wrote:
2011.04.18. 11:54 keltezéssel, Dwayne Bailey írta:
On 2011-04-17 23:33, André Schnabel wrote:
Hi,
Am 17.04.2011 20:59, schrieb Andras Timar:
I also suggest removing version number from the name of the projects,
because it has several benefits. One of them is preserving
contribution statistics of the project.
That's a good point. Statistics are important. I wonder what others
think.
I wonder why it should be important for the statistics if we have
Version numbers in the project or not. If someone is actually doing a
translation this is counted - and that is what matters (regardless of
the version she contributed to).
By using project names such as "libo-current-ui" and "libo-next-ui" you
could achieve this statistics stability, if required. The descriptive
name of the project could then communicate that this is 3.3.x vs 3.4.x
But at some point I need to move libo-next-ui to libo-current-ui and
create a new libo-next-ui. IMHO it's not a rename operation. Or is it?
Anyway, André is right, statistics per language should be enough. It
would be the best, if I didn't have to change anything in our current
setup. :)
Thanks,
Andras
--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/l10n/
All messages sent to this list will be publicly archived and cannot be
deleted
--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/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.