On Fri, Jan 30, 2015 at 12:00 PM, Gergo Tisza gtisza@wikimedia.org wrote:
On Thu, Jan 29, 2015 at 11:45 PM, Bryan Davis bd808@wikimedia.org
wrote:
The wfDebug* methods are not being deprecated officially yet but it would be great if people started treating them like they were deprecated when writing new classes.
So why not actually deprecate them?
As Bryan said I think we should, for new classes in core. They're unlikely to need backporting. https://www.mediawiki.org/wiki/Manual:How_to_debug#Logging seems to be the place to deprecate, plus the various $wg pages.
For extensions, our compatibility guidelines [1] say both * "trunk extensions only have to support current trunk MediaWiki" * and "don't break support for old MediaWiki versions unless the compatibility code is causing actual quantifiable problems." So an extension like Flow which depends on fixes to core in 1.25 might as well switch. Whatever extension developers decide, the Extension: page must express the reality of the MW version(s) it requires to work.
For sample code, it's tricky. Should mw.org have code that shows developers how to write extensions that run on latest git or on "Download MediaWiki 1.24.1", or both? (And even for the legacy LTS releases 1.23.8 and 1.19.23.)
[1] https://www.mediawiki.org/wiki/Backward_compatibility#Trunk_extensions.27_co... [2] https://www.mediawiki.org/wiki/Extension_registration