As far as I understand it, they did largely nail down addon compatibility at least around the same time as the rapid releases began. Addons hosted on addons.mo

As far as I understand it, they did largely nail down addon compatibility at least around the same time as the rapid releases began. Addons hosted on addons.mozilla.org have since last April [1] got automatic compatibility bumps each time a new version of Firefox is released. What they didn't realise was that only 25% of addons in active use were hosted on AMO, and the vast majority were self-hosted. The change referred to in this roadmap is to make the browser itself (rather than just AMO) treat extensions as compatible by default (and presumably quite a lot of supporting work to make sure that's a responsible way for the browser to behave). That change has also now landed [2]. These are important problems to tackle, but we should give credit where it's due, and it's rather more than just "on the roadmap". Justin Scott gives a good overview of their thought process and actions taken: [3] [1] http://blog.mozilla.com/addons/2011/04/19/add-on-compatibility-rapid-releases/ http://blog.mozilla.com/addons/2011/04/19/add-on-compatibili... [2] http://www.mozilla.org/en-US/firefox/10.0/releasenotes/ http://www.mozilla.org/en-US/firefox/10.0/releasenotes/ [3] http://blog.fligtar.com/2011/09/26/add-on-compatibility-progress-plans/#more-1246 http://blog.fligtar.com/2011/09/26/add-on-compatibility-prog...