On 13 February 2013 01:48, Mark A. Hershberger mah@everybody.org wrote:
I'm going to start paying close attention to people who have problems upgrading from 1.19 over the next couple of years so that when we hit the next LTS (1.25) in 2015, we'll have fewer issues for the people moving from 1.19 to 1.25.
There is near zero chance that I will keep supporting 1.19 for that long in master branch in all of my extensions (and this is assuming support for 1.19 is dropped immediately when 1.25 is released). It's already hard since 1.19 is missing some features I need.
People need to realize that they can't get the latest shiny extensions on years old MediaWiki. For extensions this would mean that they would create a branch with security fixes and other important bug fixes for 1.19. MLEB will probably just declare some release as the last release that works with 1.19.
1.19 was released on 2012-02-09. For comparison Ubuntu has released LTS version every two years.
I'd like to think that extensions in [[Category:Stable_extensions]] will be maintained, but maybe that isn't right. I certainly haven't tried all of them against 1.19.
Maintained doesn't necessarily mean support for 1.19 is kept.
Developers can help out with this. On Debian, for example, developers can announce that they're orphaning a package and it needs a new maintainer. Ideally, a developer would find someone to maintain his own extension, but if you see an orphaned extension or just don't feel like maintaining one any more, please add {{Unmaintained extension}} to its page on MediaWiki.org.
Has any extension been adopted this way?
-Niklas
-- Niklas Laxström