
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0F65F87031A45CB323AD802C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 08/23/2012 09:10 AM, Ewoud Kohl van Wijngaarden wrote:
Hello, =20 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 --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enig0F65F87031A45CB323AD802C 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/ iD8DBQFQNpk32ZIOBq0ODEERApjxAJsHBTcD+THh95YPhsY54iQ745lnvgCeOV9g VTbCqSFlZRW01AJ8ck/crd4= =j4yS -----END PGP SIGNATURE----- --------------enig0F65F87031A45CB323AD802C--