Hi, In my experience Mediawiki does a pretty good job of making the upgrade process painless - they provide admin scripts that detect version differences between software and databases, and auto-live-upgrade the database when needed. Of course it's good policy to make a back-up of both software and database to allow roll-back in the case of a problem anyway... Upgrading Mediawiki is a similar experience to manually upgrading Wordpress in terms of themes & extensions, if you have experience with that. Which extensions do we use? Cheers, Dave. On 08/23/2012 10:57 PM, Karsten 'quaid' Wade wrote:

On 08/23/2012 09:10 AM, Ewoud Kohl van Wijngaarden wrote:

...

Hello,

Currently we're running a fairly old mediawiki version (1.16) and 1.19 is out (and in EPEL-6 as mediawiki119). Should we upgrade?

Yes, that's come up in passing, although should we now be concerned about any security exploits on 1.16 to make us rush?

Otherwise, who is interested in doing or helping with this?

We also need to look to see:

* Are there changes between the versions we need to prepare for? ** Database ** Extensions ** What else? * What are the upgrade steps? * How long should we plan an upgrade to take?

- Karsten

_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

-- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62

This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA7266B37984A09FEF08109DF Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 08/24/2012 02:38 AM, Ewoud Kohl van Wijngaarden wrote:

On Fri, Aug 24, 2012 at 11:03:46AM +0200, Dave Neary wrote:

...

Which extensions do we use? =20 http://wiki.ovirt.org/wiki/Special:Version

Just in case others can't see, I see: http://www.mediawiki.org/wiki/Extension:ConfirmAccount http://www.mediawiki.org/wiki/Extension:Cite/Cite.php http://www.mediawiki.org/wiki/Extension:SupybotNotify Only the first one is a critical service, and I reckon it will likely work with the upgrade. The Cite extension could break without forcing a rollback. The SupybotNotify extension is one I think we've discussed turning off (or sending to a different channel than #ovirt), thus another non-critical extension. - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enigA7266B37984A09FEF08109DF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFQPQ3i2ZIOBq0ODEERArHPAKCytgdP2cyyLP0pH6obcsf5sU+MnQCgr3QP B0Ih/cSTEMkGKZqq9OZg2QI= =7Euo -----END PGP SIGNATURE----- --------------enigA7266B37984A09FEF08109DF--