We had quite a bit of difficulty moving from 1.18 to 1.20 because of mysterious JavaScript
timing issues in WikiEditor.
http://www.mediawiki.org/wiki/Talk:MediaWiki_vendors#WikiEditor_toolbars.2C…
On the PHP side, some protected variables in a class (I think UserMailer) got changed to
private, which broke some extensions that subclassed it. That kind of change should be
strongly discouraged, or accompanied by some new functions that access the now-private
member.
DanB
From: mnm301(a)nyu.edu [mailto:mnm301@nyu.edu] On Behalf Of Mariya Nedelcheva Miteva
Sent: Tuesday, February 12, 2013 9:23 AM
To: Daniel Barrett; Wikimedia developers
Subject: Re: [Wikitech-l] Stable PHP API for MediaWiki ?
By the way, Daniel, have you had similar problems with your next upgrades? Maybe things
have indeed improved since your post about 1.18
Mariya
On Tue, Feb 12, 2013 at 3:14 PM, Maria Miteva
<mariya.miteva@gmail.com<mailto:mariya.miteva@gmail.com>> wrote:
Hi everyone,
I guess it is a little difficult for me to describe what I mean since I am just rephrasing
what I've heard from others. I am still waiting for some more specific examples.
However, I think most people are facing the kind of problems which Daniel has so well
described in his post to the mailing list.
Maybe this quotation will help clarify things.
Mostly I want core developers to think about MediaWiki as framework with programming
interfaces for extension developers. All the changes in those interfaces have to be calm,
with slow deprecation. A role model for that is Python compiler.
(
http://www.mediawiki.org/wiki/Talk:Third-party_MediaWiki_users_discussion#F…
)
I understand from your comments that keeping things stable and preserving compatibiliy HAS
been a priority for core developers at least since Daniel's email. Is this really the
case? If this is the case, it makes me wonder why I hear some complaints about it. Is it
maybe that documentation is not clear on what will be stable and can be used and what
should not be used? Or is it a matter of educating extension developers how to find such
information?
On a brighter note, I heard that the LTS version 1.19 was the best thing that happened
since sliced bread :)
Mariya
On Tue, Feb 12, 2013 at 10:03 AM, Antoine Musso
<hashar+wmf@free.fr<mailto:hashar+wmf@free.fr>> wrote:
Le 11/02/13 19:58, vitalif@yourcmc.ru<mailto:vitalif@yourcmc.ru> a écrit :
1) removal of
global $action
2) removal of Xml::hidden()
3) broken Output::add() (had to migrate to resource loader)
4) various parser tag bugs
5) removal of MessageCache::addMessage()
6) removal of ts_makeSortable() (javascript)
7) brokage of WikiEditor adaptation
8) MediaWiki:common.js no more loading by default (security)
9) addHandler() javascript broken in IE8
Most of these were deprecations, am I correct?
I guess so. Probably methods we simply removed instead of deprecating
them like we are doing nowadays.
--
Antoine "hashar" Musso
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org<mailto:Wikitech-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikitech-l