Talk:Version check and opt-in site reporting

Ideas for options.

There should also be options like lts then stable and then alpha / wmf release and then when you select alpha it would ask you do you want updates from wmf or alpha. 86.135.251.119 23:29, 1 January 2015 (UTC)

There should also be a download link next to it so users can ether upgrade automatically or manually. 86.135.251.119 23:36, 1 January 2015 (UTC)

Right now, all upgrades will be manual, but these are good things to add. ☠MarkAHershberger☢(talk)☣ 17:47, 2 January 2015 (UTC)

Hi do you know when the updater will be released. 86.135.251.119 18:41, 2 January 2015 (UTC)

We're planning on having this in 1.25. ☠MarkAHershberger☢(talk)☣ 21:47, 2 January 2015 (UTC)

Hi what I mean do you know when it will be added for example a date or month. 151.229.249.125 22:32, 2 January 2015 (UTC)

See Version lifecycle for dates. ☠MarkAHershberger☢(talk)☣ 00:48, 3 January 2015 (UTC)

What I mean is when will the patch for using the updated be avalible in master branch 151.229.249.125 01:20, 3 January 2015 (UTC)

Updated = updater 151.229.249.125 01:21, 3 January 2015 (UTC)

Good question. We're going to be working on it ASAP, but I can't give you a date that it will be available. And, to clarify, the first round will require manual updating. ☠MarkAHershberger☢(talk)☣ 01:42, 3 January 2015 (UTC)

Ok thanks 151.229.249.125 01:43, 3 January 2015 (UTC)

Do you have a date for when the patch will be uploaded to gerrit 151.229.249.125 01:45, 3 January 2015 (UTC)

Hi is there a timeframe on when it will be avilible in git or gerrit. 151.229.250.233 17:13, 16 February 2015 (UTC)

Check

Hi Mediawiki 1.25 is almost ready to stop being developed next week will This make it into 1.25 before Tuesday or will it be added to 1.26 or add to 1.25 at a later date by back porting. 151.229.250.233 10:14, 5 April 2015 (UTC)

I don't know the actual development status, but i would say: definitely not in MW 1.25. Florianschmidtwelzow (talk) 06:26, 7 April 2015 (UTC)

Any updates on status

Hi any update on when it will be submitted to gerrit. 151.229.250.233 17:03, 19 May 2015 (UTC)

Bump. 151.227.77.167 (talk) 22:43, 23 September 2015 (UTC)

Phab task T119121 from IRC office hour

The "Version check" part of this came up in today's "Reconnecting with the shared hosting community" IRC office hour. I created phab:T119121 "implement a version check". Some relevant bits from that meeting,

 <legoktm> I'm rather interested in how shared hosting users upgrade (if they do at all), according to wikiapiary:Statistics 68.23 % of known wikis are using unsupported versions. And if people aren't upgrading to newer versions, they're not getting newer features, which seems like less of an incentive to stick with MW.
 <legoktm> gilles: I suppose the next question is, are we doing a good job promoting our new features, and is that reaching shared hosting users? The installer has an option to subscribe to mediawiki-announce, but do shared hosting users get that option if they use a different installer?
 <gilles> ... so they probably don't even know that they're running something outdated
 <gilles> #idea find (better) ways to advertise new versions/new features to shared hosting users
 <spagewmf> For updates and support, can we built into core MediaWii a parser tag <check_for_updates> and in the default install it is on the default Main_Page?
 <Trela> spagewmf: Special:Version would be a good spot to have a "New Version Available" indicator for logged in admins.
 <cscott> spagewmf: probably Special:CheckForUpdates would be better, with default permissions only viewable by admins
 <spagewmf> cscott special page works too, and the default Main_Page can transclude {{Special:CheckForUpdates}}

SPage (WMF) (talk) 21:41, 19 November 2015 (UTC)

Comments about the version check part

• Rather than a [Check for Updates Now] button, can Special:Version (optionally) just always show if your wiki is out of date? If there's a performance concern from the HTTP request, the "tell the MediaWiki installation to set up the job to check for updates" could update a MediaWiki: message string or cache the info for Special:Version to display.
• I would like the out-of-date check to be even more obvious. Perhaps the default Main_Page could transclude {{Special:Updates/status}}
• Can the wiki introspect whether it's running a release tag and by default check for updates to that? "A dropdown will allow the user to specify if they are checking LTS versions, point release updates, or major releases" is useful, but we want the appropriate "There is a dot release for this MediaWiki version/This MediaWiki version is unsupported and does not get security updates" version check message to display by default. SPage (WMF) (talk) 22:03, 19 November 2015 (UTC)

I don't think the main page is the place to check for new updates. the main page is for new visitors usually. I don't think normal editors and admins use the main page so often. I'd say Special:RecentChanges would be even more appropriate :)

I propose to have some sort of periodic reminder that pops in like a notification, for sysops only (configurable through user rights):

mw.notify( 'Latest check for updates was a month ago. Can we do a very quick check for updates now? [yes/no]', { autoHide: false } );

Or even perform the check periodically and pop the message when we detect it's outdated. Note that some installations may not have access to internet (for security reasons, etc) and thus the automatic check may fail.

The check could be done on client side, though, to save this limitation. Ciencia Al Poder (talk) 22:16, 19 November 2015 (UTC)

Ever Done?

Was this ever done? US Federal security guideline SI-2(2) requires that software under management be able to check for updates in an automated way. 96.244.147.234 (talk) 12:38, 25 July 2019 (UTC)

No, this has not yet been done. I've added a note to explain this to the top of the page. Jdforrester (WMF) (talk) 15:35, 25 July 2019 (UTC)