[Foundation-l] Why hasn't the LocalisationUpdate extension been enabled?

[Gerard Meijssen]

Hoi,
The problem with svn up is that it does not take into account that the
software run in production is not the same version that exists in SVN.
Consequently you could update messages that are no longer the same. What
LocalisationUpdate does is verify if the message in English in SVN is the
same as the one that is currently running. When the messages are exactly the
same, it follows that the localised messages are also the same.

Because the LocalisationUpdate updates from SVN, it will update the messages
that were seen by the translatewiki.net developers.

When you say the LocalisationUpdate is slow, the current update process from
SVN is slow. This however only needs to run once a day really. When this is
done when there is not much traffic anyway, it does not matter. What does
matter is that the results of a message found as a result of
LocalisationUpdate end up in the l10ncache.
Thanks,
       GerardM

2009/8/13 Tim Starling <tstarling at wikimedia.org>

> Waldir Pimenta wrote:
> > I understand why it was chosen not to always run bleeding edge versions
> of
> > the software on the live Wikimedia wikis. But the LocalisationUpdate was
> > created precisely as a workaround to this, i.e, to allow updating the
> > localisation
> > without needing to update the software.
> >
> > So my question is: why is it not enabled yet on most Wikimedia wikis?
>
> The LocalisationUpdate extension is slow, with a significant
> performance loss per page view due to DB queries, and it's
> unnecessary, because the same effect can be had with a script that
> runs svn up periodically.
>
> -- Tim Starling
>
>
> _______________________________________________
> foundation-l mailing list
> foundation-l at lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
>