Last modified: 2010-05-15 15:38:06 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 3876 - UPGRADE file should be updated with each release
UPGRADE file should be updated with each release
Product: MediaWiki
Classification: Unclassified
Documentation (Other open bugs)
All Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-11-04 02:05 UTC by Greg Hurrell
Modified: 2010-05-15 15:38 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Greg Hurrell 2005-11-04 02:05:11 UTC
MediaWiki has recently been updated from 1.5 to 1.5.1 and then to 1.5.2 but the UPGRADE file included with the distribution has a 
modification date of 5 October 2005 (prior to 1.5.1) and contains no information about those releases. It does have information 
about upgrading from early version to 1.5.

Basically, the upgrade advice amounts to "backup, install all over again, copy over customizations". The document also says, "Run the 
installer to upgrade the database schema (if necessary)", but it doesn't say where the installer is, how to run it, and how to determine 
if it is "necessary" or not.

I think that the file should be a bit clearer and also updated for each release. It should have headings like "Upgrading from 1.5.1 to 
1.5.2" and "Upgrading from 1.5 to 1.5.1". There doesn't need to be a lot of information under these headings. It could even be 
something like: "Copy the files from the new version over the old ones. There is no need to update the database schema or run any 
upgrade scripts." For really minor upgrades (where only a few files change), you could write, "The following files are new for this 
version:..." But it would be reassuring for users if there were specific instructions for each new version and some mention of the 
scope of the changes.

For the record, I've made my own notes for these minor upgrades. They would need to be adapted to suit other people's systems, but 
they work for me:

* download new build
* extract 
* read UPGRADE
* copy LocalSettings.php into new install
* remove config directory from new install
* change ownership in new install directory (where you substitute appropriate values for your system for "root" and "apache"):
    chown -R root:apache .
* change permissions in new install directory:
    chmod -R o-rwx .
* move old install to ~/public_html/oldwiki (or appropriate path for your system)
* move new install to ~/public_html/wiki (or appropriate path for your system)
* check upgraded wiki version via web browser:
* remove old install directory

Related bug: bug #198.
Comment 1 Brion Vibber 2005-11-04 02:06:32 UTC
The instructions remain the same unless some major change has occurred that requires 
different directions.
Comment 2 Greg Hurrell 2005-11-04 09:04:51 UTC
Fair enough. I still think the instructions are woefully inadequate though.

Note You need to log in before you can comment on or make changes to this bug.