The download page for 1.17 has the (somewhat scary) comment:
If your MediaWiki installation is heavily modified, it may be difficult to
incorporate the latest official changes/updates. (So here's version 1.6.5.
It's good for maybe a year.)
I accept the need to do whatever integration is necessary-especially since
the one-year clock has been ticking for a while now--but I need to know:
a) What constitutes "heavy" modification?
--We have a installed a number of plugins, have defined some variables,
have created several customized skins. Is that heavy or light?
b) What, in general, should be the migration process?
I'm guessing there are other kinds of modifications that could be done.
So ideally the upgrade notes would include a taxonomy of cases:
- If you've done "X", you'll need to do "Y".
etc.
The answers to those questions will help to tell me how much time an upgrade
is likely to take.
tia!
eric
~~~~~~~~~~~~~~~~~~~~
Eric Armstrong
Developer Advocate/Evangelist
www.longjump.com <http://www.longjump.com/>
lj.platformatyourservice.com/wiki
LongJump provides a cloud-computing platform that makes it
easier to develop & deploy database-driven apps. Build from scratch
or starting from a rich suite of customizable "application templates".
The platform and its collaboration capabilitites can be either self-hosted
or shared. It comes with a complete suite of Java and REST APIs,
integrated testing, and an Eclipse plugin.
~~~~~~~~~~~~~~~~~~~~
Eric Armstrong
Developer Advocate/Evangelist
<http://www.longjump.com/>
www.longjump.com
lj.platformatyourservice.com/wiki
LongJump provides a cloud-computing platform that makes it
easier to develop & deploy database-driven apps. Build from scratch
or starting from a rich suite of customizable "application templates".
The platform and its collaboration capabilitites can be either self-hosted
or shared. It comes with a complete suite of Java and REST APIs,
integrated testing, and an Eclipse plugin.