Jump to content

Topic on Template talk:DownloadMediaWiki

Managing "versions" is painful

3
Reedy (talkcontribs)

We ended up in a situation where the template was saying 1.36 is an LTS... This isn't true.

To users of MediaWiki versions version 1.34 and earlier: These versions are no longer supported. Please update to a newer version of MediaWiki:

    MediaWiki 1.37.0 (download .zip, download .tar.gz) - stable
    MediaWiki 1.36.2 (download .zip, download .tar.gz) - current long-term support (LTS)

This weird way of using commented templates, use of void, HTML comments etc is painful to manage. Why "legacy release" was used for LTS... I have no idea

* MediaWiki {{MW legacy release number}} ({{MW legacy release link zip|1=<translate><!--T:40--> download <tvar name=1>.zip</tvar></translate>}}, {{MW legacy release link|1=<translate><!--T:41--> download <tvar name=1>.tar.gz</tvar></translate>}}) - <translate><!--T:49--> current long-term support (LTS)</translate>

Never mind there seems to be numerous duplicates...

Jdforrester (WMF) (talkcontribs)

I just re-implemented the equivalent logic for MWReleases; clearly we should have this as a single Module we can just call to output a list of currently-supported branches, linking either to their download targets or release pages or something else…?

Ciencia Al Poder (talkcontribs)

The idea of the templates and logic was to preserve the translation units, so things don't have to be re-translated again for new releases, because sometimes a legacy lts doesn't appear and sometimes it's present.

Maybe a module would be a good idea, and add the translatable text as invocation parameters so they can be used when generating the output, even if sometimes they're not used

Reply to "Managing "versions" is painful"