Template talk:MWReleases

Template:MW quick download

It would be nice to include some of the links of Template:MW quick download here, or at least the name of the last 1.x.y release for each 1.x recent release. --Nemo 09:38, 20 January 2013 (UTC)

Translate

Could someone please mark this for translation? LegoFan4000 (talk) 19:43, 14 May 2017 (UTC)

LTS documented inconsistently.

According to the Version_lifecycle, MW version 1.27 is still the active LTS release. With the MW release 1.29, 1.28 is not being displayed as the LTS release by this template. Has their been a policy change, or is something simply broken with templates/LUA scripting this sidebar uses?

This template was borked somehow. Just fixed it. Thanks for the note. Cheers --[[kgh]] (talk) 19:54, 13 July 2017 (UTC)

MW 1.31

MW 1.31 is missing, only 1.30 and 1.32 is shown. Should there be a beta or release candidate entry? --121.214.98.204 13:12, 27 May 2018 (UTC)

{{MWReleases}} and {{MWReleases/en}}

In {{MWReleases/en}}, the box says that 1.32 is the LTS version. I think it remains from when 1.31 was the stable one. The strange things is that I cannot modify because it is said to be a translation of {{MWReleases}}. Can someone help me ? Thank you, Jona (talk) 08:33, 11 January 2019 (UTC)

After editing {{MWReleases }}, the page should be marked for translation by a translation administrator. Then the system updates all translation pages like {{MWReleases/ja }}, {{MWReleases/en }}, etc. --Shirayuki (talk) 11:07, 11 January 2019 (UTC)

Future version

At the moment, in the infobox, we have :

• MediaWiki 1.31 (LTS)
• MediaWiki 1.32 (stable)
• MediaWiki 1.34 (alpha; git master)

MediaWiki 1.33 is missing (and should be there IMHO). In the template we load the LTS, the stable and the alpha version but 1.33 is the beta version. Although we can just replace the alpha by the beta, it don't think it's a future-proof solution. Maybe we have to compare the stable, the beta and the alpha to decide which one should be shown. Any remark is welcome. Jona (talk) 09:41, 10 May 2019 (UTC)

@Jona: Good idea. Done. Jdforrester (WMF) (talk) 16:31, 10 May 2019 (UTC)

@Jdforrester: Waouw, what a reactivity ! Thank you :-) Jona (talk) 08:15, 11 May 2019 (UTC)

Current LTS reported as "Legacy" (1.35.7, 2022-07-01)

It doesn't seem right to me that the template uses the phrase "Legacy Long Term Support" for the current LTS version. I can't be sure whether this was a a semantic choice or a template logic thing. I know "legacy" and "unsupported" are not the same thing, but it's often enough people use "legacy" to imply the lack of support and a lingering pressure to move away from it. I think calling a Long Term Support version "legacy" creates unnecessary ambiguity. It's actively maintained.

Calling 1.27 or 1.31 "legacy long term support" would be fine, though.

If this were in an article, I'd probably just make the change myself and see if people prefer to reverse it, but since these are clearly carefully maintained templates, I wouldn't dare. So if anyone with an interest wants ot consider it, or share another perspective, that's all I can ask.

Or, maybe I'm just acting out the "euphemism treadmill". Thanks for reading. :) 128.231.234.25 18:25, 1 July 2022 (UTC)

Part of the template's text is not marked for translation

By this, I mean that one can translate whether the version is alpha, beta, stable, LTS or legacy, but not the part of the sentence before or after. Alfa-ketosav (talk) 10:07, 3 January 2023 (UTC)