Topic on Talk:Third-party MediaWiki users discussion/Flow

• What are the main recurring pain points of installation and upgrade?
• What would you like to see in notes for main releases like MediaWiki 1.20, or security releases notes? What have you liked or missed in the past, and what convinces you to upgrade?
• Would you like a notification on your wiki about possible upgrades (as Joomla, Wordpress etc. do in their admin panels) and where?
• Please add/comment on Suggestions for extensions to be integrated the extensions which are most often/always needed.
• What are the configuration settings defaults or default user options which most often/always need to be changed locally nowadays?

Core upgrading works very well. But extension upgrading suffers from complexity issues in our experience. I understand that some things are too difficult to tackle but others I believe could be improved. I will open a new thread "Improving extension updating" for that...

Quoting an email from http://www.softaculous.com/.

MediaWiki upgrades do cause some pain to users because after unzipping the user needs to go as many steps as installing a new version of MediaWiki. It would be great if you could add a silent upgrade script which will upgrade the installation without any user intervention.

At least half a dozen sysadmins wrote me that we should really have an updater as Joomla or Wordpress have.

It would be great to have a mechanism that allows extensions to add "steps" to the install/update wizard. I.e. when installing MW there is a section that lists all bundeled extensions. If the user selects the extensions for automatic install they are automatically included at the end of LocalSettings.php. But there is no way to configure the extensions during the installation process.

Help testing the Extension:Configure is appreciated, I think.

Please consider requesting a slot at QA/Weekly goals.

This post was posted by Qgil-WMF, but signed as Qgil.