News for hackers. Stuff that matters.
Re:Postmortem on a beta regression by numlocked on Tuesday January 26, 2016 @04:16PM (#10976138)
This is attributing an awful lot of malice to the FF team. They acknowledged they were wrong and got the fix out. Sometimes it takes a bit of pushing to understand the impact of a bug; we've all been there.

The entire post is about recommendations to avoid this sort of thing in the future and make the FF dev process friendlier for add-on developers. Reading your comment it sounds like their attitude towards add-on devs is "go pound sand", but it certainly doesn't seem like it to me based on this post.

Re:Postmortem on a beta regression by semi-extrinsic on Tuesday January 26, 2016 @04:25PM (#10976214)
I never ment to imply any malice. (A famous quote comes to mind.) I'm just saying that (as Ben pointed out):

* the bug breaks the browsing experience for millions of users

* the fix is well-understood and simple: re-add a single file that was accidentally omitted.

Closing that as a WONTFIX is.. bad.

Re:Postmortem on a beta regression by dolske on Tuesday January 26, 2016 @08:37PM (#10977639)
Hindsight is 20/20, but when the wontfix decision was made it wasn't clear that there was significant impact beyond the one addon which reported it -- which had already implemented and shipped a simple workaround -- and the missing file had been missing for nearly 2 months on beta. This was just a few days before shipping already-final code to hundreds of millions of people, which isn't a time to be taking changes lightly. (And as a fun hindsight-in-hindsight twist, it now turns out the millions-of-users addons wasn't actually as badly broken as described.)

It all worked out ok in the end, and could have taken a much better path, but it's not as egregious an issue as you make it out to be. A mistake was made, and it got fixed as soon as we realized it was a mistake.

Re:Postmortem on a beta regression by kazinator on Tuesday January 26, 2016 @05:45PM (#10976838)
Reading the bug comment history, it seems they were saying "won't fix for 44 (too late)" not "won't ever fix, amen!"

But installations of 44 will be out there for who knows how long; affected add-ons would have to carry the workaround egg-corn for a long time before declaring no support for 44 and removing it.

Re:Postmortem on a beta regression by cpeterso on Tuesday January 26, 2016 @04:47PM (#10976380)
The affected add-on, or at least the one that prompted the bug report to be filed, has 46,755 users, not millions:

https://addons.mozilla.org/en-US/firefox/addon/new-tab-overr...

Re:Postmortem on a beta regression by semi-extrinsic on Tuesday January 26, 2016 @05:38PM (#10976779)
The add-on Ben was talking about is a different one (I don't know which).
Re:Postmortem on a beta regression by cpeterso on Tuesday January 26, 2016 @07:35PM (#10977400)
Thanks. I missed that because the other addon's name was never mentioned.