https://bugzilla.wikimedia.org/show_bug.cgi?id=28863
--- Comment #7 from Chad H. <[email protected]> 2011-08-10 20:28:35 UTC --- (In reply to comment #6) > Not a 1.18 blocker, and one that we shouldn't do for the sake of doing. If > there's a feature that we're working on that breaks these, then we can remove > them as part of that work, but we shouldn't break backwards compatibility just > for giggles. Well stuff that's already marked for deprecation can be slowly phased out once extensions have all been updated (and then the general consensus is to wait at least one more release). When we mark stuff @deprecated these days we generally mention when they were first deprecated so we can properly remove them over time. But yes, removing deprecated code shouldn't be a blocker unless it's breaking something by remaining there. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
