Bugzilla

So, today we released Bugzilla 3.2.1, which fixes the longest-standing security bugs in Bugzilla, in addition to a few other security issues. These long-standing security issues were actually public for many years, but it required a lot of ... [More] re-architecture of Bugzilla before we could fix them.We also released 3.3.2, which has a lot of cool new features, not the least of which is hiding email addresses from logged-out users.And we put out Bugzilla 3.0.6 and Bugzilla 2.22.7 as security fixes for people still using those older branches.Anyhow, you can read the news announcement for more details, and the Security Advisory if you want to read up on the security issues that were fixed.It feels really great to have these releases out. Although I haven't ever heard of a successful exploit of these security issues, they've been around for so long that it was naggingly worrying to have them there, and it's a huge relief to have them fixed and see the fixes released!Anyhow, here's a bit of news about Bugzilla trunk, which will be Bugzilla 3.4:- Our current estimated release date is sometime in May, but that's a very rough estimate.- We're now in a soft freeze (since Jan 29), which means that enhancements that had patches before Jan 29 can still go in, but any enhancements that didn't have patches at that time can't go in. This allows existing patches some time to pass review and to clean up any feature work that wasn't quite done before the freeze.- There are a few nice enhancements that should still be coming, including a simplified bug entry page.- If there are any other long-term major problems that you see in Bugzilla that we haven't fixed in 3.4, please let me know. Point me at a bug, or anything you want. And I don't mean minor things, like the positioning of a button or some text on a page, but big things like how emails used to be displayed to logged-out users. :-)-Max [Less]

A quick note to let you know that Bugzilla 3.3.2, 3.2.1, 3.0.7 and 2.22.7 should be released on Monday (in two days). All security patches have been reviewed, all blockers have been fixed, and release notes are also ready. Those are important security releases, do no miss them! – Un mot rapide pour vous dire que Bugzilla [...]

For those using bugzilla.mozilla.org, I wanted to let you know that when we upgraded to 3.2, you got access to a new Bugzilla skin called "Dusk." Though I've been attempting to convince the admins of the site to switch bugzilla.mozilla.org over to ... [More] usnig Dusk by default, it hasn't happened (yet?). So, I wanted to let you know that you can change Bugzilla's skin to Dusk yourself, using the General Preferences page. Dusk is much nicer than the Classic skin, in my opinion, and I think Bugzilla actually becomes more usable with it. If you want to see what it looks like before you switch over to it, you can either use the "View > Page Style" menu in Firefox, or you can look at our test installation, which defaults to Dusk. -Max [Less]

For those using bugzilla.mozilla.org, I wanted to let you know that when we upgraded to 3.2, you got access to a new Bugzilla skin called "Dusk." Though I've been attempting to convince the admins of the site to switch bugzilla.mozilla.org over to ... [More] usnig Dusk by default, it hasn't happened (yet?). So, I wanted to let you know that you can change Bugzilla's skin to Dusk yourself, using the General Preferences page. Dusk is much nicer than the Classic skin, in my opinion, and I think Bugzilla actually becomes more usable with it. If you want to see what it looks like before you switch over to it, you can either use the "View > Page Style" menu in Firefox, or you can look at our test installation, which defaults to Dusk. -Max [Less]

For those using bugzilla.mozilla.org, I wanted to let you know that when we upgraded to 3.2, you got access to a new Bugzilla skin called "Dusk." Though I've been attempting to convince the admins of the site to switch bugzilla.mozilla.org over to ... [More] usnig Dusk by default, it hasn't happened (yet?). So, I wanted to let you know that you can change Bugzilla's skin to Dusk yourself, using the General Preferences page. Dusk is much nicer than the Classic skin, in my opinion, and I think Bugzilla actually becomes more usable with it. If you want to see what it looks like before you switch over to it, you can either use the "View > Page Style" menu in Firefox, or you can look at our test installation, which defaults to Dusk. -Max [Less]

For those using bugzilla.mozilla.org, I wanted to let you know that when we upgraded to 3.2, you got access to a new Bugzilla skin called "Dusk." Though I've been attempting to convince the admins of the site to switch bugzilla.mozilla.org over to ... [More] usnig Dusk by default, it hasn't happened (yet?). So, I wanted to let you know that you can change Bugzilla's skin to Dusk yourself, using the General Preferences page. Dusk is much nicer than the Classic skin, in my opinion, and I think Bugzilla actually becomes more usable with it. If you want to see what it looks like before you switch over to it, you can either use the "View > Page Style" menu in Firefox, or you can look at our test installation, which defaults to Dusk. -Max [Less]

For those using bugzilla.mozilla.org, I wanted to let you know that when we upgraded to 3.2, you got access to a new Bugzilla skin called "Dusk." Though I've been attempting to convince the admins of the site to switch bugzilla.mozilla.org over to ... [More] usnig Dusk by default, it hasn't happened (yet?). So, I wanted to let you know that you can change Bugzilla's skin to Dusk yourself, using the General Preferences page. Dusk is much nicer than the Classic skin, in my opinion, and I think Bugzilla actually becomes more usable with it. If you want to see what it looks like before you switch over to it, you can either use the "View > Page Style" menu in Firefox, or you can look at our test installation, which defaults to Dusk. -Max [Less]

Bugzilla 3.3.1 has been released last night and is the first development snapshot of what will become Bugzilla 3.4, whose feature freeze date is January 29, 2009. More important new features are available in the last Status Update: users can choose ... [More] their timezone to display dates and times (especially in bug comments), several improvements to [...] [Less]

I don't know what's happened, but for some reason, but in just the last month or so, we've fixed almost every single long-term performance problem, security issue, and common support issue in Bugzilla. All of the sudden we've been really productive ... [More] on attacking things that have been sitting around for just too long.I suppose here's what happened:1. We got out the Bugzilla 3.2 release, so we didn't have all our attention on that anymore.2. Our architecture is finally at a point where it doesn't occupy all our attention just to maintain Bugzilla, and we're also not spending all our time fixing the architecture. So now we can actually focus on cleaning up all of this old "dirty laundry".3. I finally started applying The Feature Acceptance Test to Bugzilla, which woke me up and suddenly made it really easy to prioritize things and realize what I need to focus on fixing. "Oh, what blocks Bugzilla from helping people fix bugs?", "Which of these features will most help people fix bugs?"--just asking these questions made it really easy for me to suddenly have a workable priority list.Anyhow, whatever the reasons are, I'm really happy that we're doing it and I hope it keeps up! :-)-Max [Less]

I don't know what's happened, but for some reason, but in just the last month or so, we've fixed almost every single long-term performance problem, security issue, and common support issue in Bugzilla. All of the sudden we've been really productive ... [More] on attacking things that have been sitting around for just too long.I suppose here's what happened:1. We got out the Bugzilla 3.2 release, so we didn't have all our attention on that anymore.2. Our architecture is finally at a point where it doesn't occupy all our attention just to maintain Bugzilla, and we're also not spending all our time fixing the architecture. So now we can actually focus on cleaning up all of this old "dirty laundry".3. I finally started applying The Feature Acceptance Test to Bugzilla, which woke me up and suddenly made it really easy to prioritize things and realize what I need to focus on fixing. "Oh, what blocks Bugzilla from helping people fix bugs?", "Which of these features will most help people fix bugs?"--just asking these questions made it really easy for me to suddenly have a workable priority list.Anyhow, whatever the reasons are, I'm really happy that we're doing it and I hope it keeps up! :-)-Max [Less]