2015-08-26 8:45 GMT+02:00 Brian Wolff bawolff@gmail.com:
This seems kind of backwards. A bunch of changes were made, things exploded, and now Community tech is going to try to desperately fix them.
Maybe this is a sign we need to re-evaluate how we do client-side deprecations.
I couldn't agree more: since document.write has been deprecated and non ResourceLoader-enabled gadgets have been disabled, tens of gadgets have been broken on many wikis, some of them being actually used by many editors. Now, three weeks later, all gadgets have not yet been fixed, the breaking changes have not been temporarily reverted and angry users are still complaining almost everyday about stuff being broken.
What about fixing first and deprecating after? At least when it's technically feasible like for code in the MediaWiki: namespace.
BTW, thanks to Ryan and Ori for their precious help in fixing what remains broken on the French Wikipedia!