On 5 April 2014 08:17, Jeroen De Dauw jeroendedauw@gmail.com wrote:
Hey,
Is anyone working on resolving this issue?
What issue?
The current state means that extension authors need to either
- use if-else checks based on MediaWiki versions
- live with having deprecation notices on 1.23
- break compatibility with 1.22 and earlier
Or am I missing something?
Yes. You're meant to:
- write your extension for $CURRENTVERSION; - Note that extensions are branched automatically when $CURRENTVERSION increments - users use the extension's branched version (e.g. REL1_22) for $THEIRVERSION; and - backport really urgent fixes from $CURRENTVERSION to old versions.
If you *also* want to backport bug fixes and new functionality to older branched versions, that's great, but a lot of work. You may need to version each release branch for sanity if you have lots of these. It's generally worthwhile prioritising bug fixes over new functionality, and prioritising support for the versions of the extension matching the LTS versions of MediaWiki, as that is likely to be where many downstream users are.
J.