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

[Gerard Meijssen]

Hoi,
When a back port is created, There is *a lot of manual work* involved in
preparing the messages that are relevant to a specific release. As it is,
translatewiki.net localises the latest development versions of software and
this is not what runs in production. The key functionality of
LocalisationUpdate is that it ensures that the messages it imports are
compatible with the version of MediaWiki that runs in that instance of the
software, including extensions.

Probably LocalisationUpdate could work with the 1.15 stable version of
MediaWiki. This would be really valuable for all the MediaWiki installations
out there that have "another" language as default. It would even be an
incentive to them to localise MediaWiki at translatewiki.net because they do
not have to wait for the next release.
Thanks,
     GerardM

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

> Gerard Meijssen wrote:
> > 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.
>
> Apparently that's not a problem for the release branches, which often
> receive backported message updates from translatewiki.net. Why can't
> the same backporting be done for the wmf-deployment branch?
>
> -- Tim Starling
>
>
> _______________________________________________
> foundation-l mailing list
> foundation-l at lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
>