We released Bugzilla 3.4 today, which also means Bugzilla 2.x is EOL (including Bugzilla 2.22). Here is a quick (and incomplete) list of new features/improvements compared to Bugzilla 3.2:
- The page to file bugs is now simpler, with "advanced" fields being hidden by default.
- The home page has been redesigned to be easier to use by new users.
- Logged out users can no longer see email addresses of other users at all, to prevent spam. Only the name of users is displayed.
- All passwords are now encrypted using SHA-256 instead of the crypt() function. This means passwords can now be longer than 8 characters.
- It’s now possible to send emails asynchronously when updating bugs (default: off), so that your browser doesn’t have to wait for all emails to be sent before displaying the page.
- Dates and times in comment headers and in emails are now displayed using your timezone instead of using the server timezone. Set your timezone from your Preferences panel.
- Several improvements to custom fields (new species of custom fields, as well as the possibility to display them under some given conditions).
- You can now reorder columns to display in buglists. Till now, you could only choose which columns to display, but you couldn’t reorder them. This is now possible.
- By default, obsolete attachments are hidden when viewing a bug. You can click the "Show obsolete" link to display them.
- You can use custom drop-down fields in tabular and graphical reports.
- Many new webservice methods.
If you are still using Bugzilla 2.x, or a development snapshot (3.3.x), you are highly encouraged to upgrade to 3.4. Also, if you are already running Bugzilla 3.2.x, the upgrade to 3.4 should be straightforward as there is no charset conversion (remember when we moved to UTF8 in 3.2), and almost no DB changes (besides new foreign keys to ensure your DB integrity). Note that you should run sanitycheck.cgi and fix errors reported by this script before upgrading, to avoid problems later.
I just configured Majordomo to set headers correctly when sending emails to the firstname.lastname@example.org mailing-list so that the "Reply To All" option in Thunderbird will work as expected. Blake Winton (working for Mozilla Messaging) thought this would be a good idea to blog about it.
Majordomo was configured to override the Reply-To header and replace it by email@example.com. The goal is to help broken email clients which don’t understand list headers. The problem with this configuration is that "Reply To All" only replies to the mailing-list, which is a problem when the sender of the initial email is not in the mailing-list. And if you don’t pay attention to this, you will forget to CC him and the guy will never get any reply. I considered this as a bug and reported it on b.m.o as bug 505374.
To fix the problem, I had to add the following two lines to the ‘message_headers‘ parameter in Majordomo:
List-Id: QA Bugzilla <$LIST@$HOST>
I also had to set the ‘override_reply_to‘ parameter to ‘no‘ and leave the ‘reply_to‘ parameter empty, instead of the existing
$LIST@$HOST value. This way, the original Reply-To header, if present, is no longer overriden and the "Reply To All" option will send the original sender a reply, as expected. Thanks to the List-Id and List-Post headers, Thunderbird 3 will also offer you the "Reply To List" option, which lets you reply to the mailing-list only. And you can also choose the usual "Reply" option to reply to the sender only, ignoring the mailing-list.
I’m really irritated that in 2009, a CD player is still unable to work correctly when there are two CD drives connected to your PC. I’m pretty sure cdplayer.exe was working fine in Windows 95 with two drives, but 15 years later KsCD is still unable to work correctly. Listening to music, and especially audio CD, is one of the most basic features in an OS which should work like a charm, without any configuration needed from the user (audio CD detected > open the default CD player > play music *automatically*).
I’m on Mandriva Linux 2009.0, with KDE 4.2.4, and KsCD is BROKEN! Not only it’s unable to play any CD, but there is no longer a way to specify which drive to look at to find a CD (this feature was available with KDE 3.5). I tried Grip too, but it doesn’t work (it can list tracks, and that’s it). I tried Mplayer, but it cannot even read audio CDs (!!). And VLC 1.0.0 has a bug which prevents it to read some tracks (no idea why). This leaves me with the old XMMS application and the CDread input plugin. To have it to work, you have to use phonon-xine in the backend because phonon-gstreamer is broken! XMMS is working fine, except that if you eject the CD while XMMS is still playing it, XMMS thinks it’s a good time to freeze your PC. Wow! Welcome in the 21st century, Linux! (and some people still wonder why Linux is still at 1% of the market share??)
For those interested in this story about KsCD, Xine and GStreamer, please read this bug and especially links in comment 17:
We had a Bugzilla meeting yesterday, and one question was about the number of downloads of recent releases. Bugzilla 3.4rc1 and 3.2.4 were released last week, on July 8, i.e. 6 days before the meeting. There were 1204 downloads of Bugzilla 3.4rc1, and 4426 downloads of Bugzilla 3.2.4 so far. These numbers look low to us, but maybe that’s due to summer vacations. But the good news is about Bugzilla 3.2.3, which was released on March 30, i.e. 3.5 months ago: 131235 downloads! This number is consistent and slightly higher than for Bugzilla 3.0.4 (released on May 4, 2008), which has been downloaded 120500 times after the same time.
One year ago, I blogged about major Bugzilla installations and the version they were running. Many of them were running the latest Bugzilla version available. I think it’s interesting to see what these installations are running today. The number in brackets is the version which was used in August 2008.
- ClamAV: 3.4rc1 (2.22.3)
- Mozilla: 3.2.4 (3.0.4+)
- KDE: 3.2.3+ (3.0.5)
- RedHat: 3.2.3+ (3.1.4+)
- WebKit: 3.2.3 (2.20.1)
- Apache: 3.2.3 (3.0.4)
- Wine: 3.2.3 (3.0.4)
- Mandriva: 3.2.3 (3.0.5)
- OpenSSH: 3.2.3 (3.2rc1+)
- kernel.org: 3.2.2 (2.22.2)
- Novell: 3.2.2 (3.0)
- WikiMedia: 3.0.8 (3.0)
- FreeDesktop: 3.0.8 (3.0.3)
- Songbird: 3.0.5 (3.0.4)
- W3C: 3.0.4 (unchanged)
- Facebook: 3.0.4 (unchanged)
- Eclipse: 3.0.4 (unchanged)
- ActiveState: 3.0.3 (unchanged)
- Itos (NASA): 3.0.2 (unchanged)
- Samba: 2.22.1 (2.20)
- Maemo: 2.22.1 (unchanged)
- Yahoo!: 2.22.x (unchanged?)
- Gentoo: 2.22 (unchanged)
- Gnome: 2.20.5 (unchanged)
- GCC: 2.20+ (unchanged)
- OpenOffice: 2.11 (unchanged)
We can see a few major upgrades (especially ClamAV, WebKit, and kernel.org), but many of them didn’t upgrade at all in the last 11 months. All those installations are unfortunately vulnerable to different security bugs. Keep in mind that Bugzilla 2.20.x is no longer supported, and that the support for 2.22.x will stop at the end of the month, when Bugzilla 3.4 will be released.
We released Bugzilla 3.4rc1 and 3.2.4 a few minutes ago. If everything goes well, there won’t be a 2nd release candidate for 3.4, and so 3.4 could be released later this month or next month. New features in 3.4 compared to 3.2 are listed in the release notes. Both releases also contain one minor security fix. If you were running Bugzilla 3.3.x, you are highly encouraged to upgrade to 3.4rc1 asap.
If you are still running Bugzilla 2.22.x, keep in mind that we will stop supporting it when Bugzilla 3.4 is released. So you should upgrade to 3.2.4 (or 3.4rc1) very soon now.