Release notes should really include the release notes

A new version of the Firefox browser was released today. A minor update from version 2.0.0.6 to version 2.0.0.7.

Even more minor than that, actually, since what came out was just an RC version for testing. Sometime in the past I downloaded an update that was considered a beta or RC, so I’m on the list to keep getting them on the automatic updates.

The problem is that there was no information provided on what exactly the update includes, and what is the purpose behind it. The release notes page did not contain any relevant info (I’m not promising they won’t change the page in the future. It doesn’t contain the info now, and haven’t for quite a few hours so far).

It had lots of other things, the general outline they put on each release-notes page. But the actual release notes, what was changed from the last version, no. Nothing.

There wasn’t even any link to a page where this information could be found. Because, well, in theory it would have been that exact same page.

That’s a very very poor way to roll out an update. If you ask someone to install a new version of a software, and especially if it’s a beta/RC that you want people to test and provide feedback for, you have to tell them why and what has changed.

Seems very sensible to me. Apparently doesn’t seem so sensible to some of the people in the Mozilla foundation. Don’t get me wrong, they’re doing a great job, and Firefox is terrific. But most people don’t follow all the bugs and progress on every single application they use, so it’s far from obvious what an update is for.

I do hope they’ll do better next time. I’m more than willing to install updates, but I need to know why.

In this particular case, if someone is interested, it’s a single fix for a single security vulnerability. Well, a potential whole class of problems, but only a single known point. Which was now actually more of a problem with the Quicktime plug-in (on Windows) and not in Firefox itself, but in this case it’s a good idea to fix it in Firefox as well, to prevent any future problems from the same direction. You can look at the actual bug report for more technical information, if you really want to.

Leave a Reply

You must be logged in to post a comment.