Last modified: 2010-05-15 15:48:33 UTC
Here are some comments on file "UPGRADE"
Having downloaded the desired new version of the software, either as a package
from SourceForge, or via an export from Subversion, decompress the files as
needed, and replace the existing MediaWiki files with the new.
Note that reading that, many people will just untar into existing
directories, so any old unused php files will just accumulate if they
don't get overwritten.
Much different than the developer's world where one only sees current
Perhaps tell them to untar into newdir, copy
* The LocalSettings.php file
* The AdminSettings.php file, where it exists
* The extensions directory
* The images directory
into newdir, then move dir to olddir and newdir to dir. And if all is
OK one day rm -r olddir.
Or no big deal if you can guarantee that the accumulating crud won't bite
one one day.
=== Perform the database upgrade ===
From the command line, browse to the maintenance directory and run the
update.php script to check and update the schema. This will insert missing
tables, update existing tables, and move data around as needed. In most cases,
this is successful and nothing further needs to be done.
Too bad you blur "update" and "upgrade". I would say
=== Perform the database update ===
or change update.php to upgrade.php.
At least in Debian apt parlance, update and upgrade are very
different. Here you upgrade actually.