2.0.10 was tagged 8 months ago and a lot has happened since then. Time to actually tag 2.0.11?

(In reply to Serge Gautherie (:sgautherie) from comment #1) > 2.0.10 was tagged 8 months ago and a lot has happened since then. > Time to actually tag 2.0.11? s/tagged/branched/g

(In reply to Serge Gautherie (:sgautherie) from comment #1) > Time to actually tag 2.0.11? Or maybe 2.1, as you see fit. I'm not sure whether you want to continue with "pre" scheme + branching, or just discontinue both and just work on 'default'. NB: Fwiw, ChatZilla and Venkman do the latter, but it's up to each project to choose. SeaMonkey needs to update the revision it is bundling before next cycle (= soon) and would prefer to use an official version.

(In reply to Serge Gautherie (:sgautherie) from comment #3) > SeaMonkey needs to update the revision it is bundling before next cycle (= > soon) and would prefer to use an official version. I agree with DOMi could go for a new official version, since there are l10n changes on its trunk as well :-) That said, SeaMonkey is not blocked on this, I updated the compat bump on the 2_0_10 branch, as per my norm.

(In reply to Justin Wood (:Callek) from comment #4) > I updated the compat bump on the 2_0_10 branch, as per my norm. Ftr: bug 730690.

DOM Inspector 2.0.11 release will go out next Wednesday, March 21 to allow more time for the Swedish and Polish localizations, since those are reasonably active localizations that are not currently up to date. I have filed bug 736606 and bug 736607 for this purpose, and to notify interested parties.

(I'd forgotten about en-GB. I just filed bug 736625 for that.)

(In reply to Colby Russell :crussell from comment #7) > (I'd forgotten about en-GB. I just filed bug 736625 for that.) That's been fixed now.

Changeset 2d1da3662aec for bug 733373 was backed out, since AMO refuses to accept fx/tb/sm version strings which are greater than all options available on AMO (currently 14.0a1). http://hg.mozilla.org/dom-inspector/rev/2d1da3662aec DOM Inspector was prepared for release without the changed install.rdf version strings. http://hg.mozilla.org/dom-inspector/rev/b6de3a5ce573 http://hg.mozilla.org/dom-inspector/rev/453ac97308b3 2.0.11 is now awaiting review on AMO.

2.0.11 is now available on AMO.

I verified in SM 2.10 and SM 2.11 logs that they package DOMi 2.0.11 now.