I fully understand and empathize with the reaction that has happened and now that Mozilla (my employer) has a statement apologizing and committing to a public post-mortem (which I fully support) to the folks who are raising issues with the timing and sequence of events leading up to the response itself since Friday (I won't comment on the incident itself, since that's the job of the post-mortem) I wanted to mention one thing that may help add some human perspective:

Mozilla is a distributed organization and was on the last day of its in-person, week-long, bi-yearly all-hands meeting in Austin on Friday when this started. At the time, and through large parts of Saturday, many Mozillians were in last-minute meetings, airports, in the air, or on the road, and were all concluding a week's worth of meetings where everyone was getting face time with collaborators and hashing out in person what we're doing for the next 6 months.

I was not involved, but you can imagine that when trying to decide what to do in response to something like this that many people need to coordinate. So it was a bit of a perfect storm of having tired humans, many of whom were in and out of internet access, etc.

edit: I fully understand the frustrated replies -- as I mentioned I personally feel that the reaction by the community to what happened was justified -- I wrote this not to comment on what happened (as noted in the post, Mozilla has publicly committed to a post-mortem) but wanted to provide this info about this unfolding when a lot of people were traveling, etc. I was happy and thankful to see this posted today and our rollback of the add-on over the weekend and hope that the follow-ups planned help us learn and move forward in a way that the community supports.