Bugzilla 3.0rc1 released

Bugzilla 3.0rc1 has been released.  Max has more details.

As Max mentions, this really is a release candidate this time instead of a “late beta” like some of our previous release candidates have been in the past.  So to anyone who is maintaining a localization pack for Bugzilla, now’s the perfect time to update it for Bugzilla 3.0, since what’s in the templates now is pretty much what’ll be there for the final release, unless any major regressions are found.

MythTV rocks

I’ve been toying with the idea of setting up a MythTV box on and off for a while, and with family members complaining about the difficulties of getting a VCR programmed for the correct time, the allure of a DVR where you could just point it at a show in the program schedule and say “record this” was getting high.  Just before Christmas, I ran across a new startup company selling preconfigured dual-tuner Home Theater PC boxes with Ubuntu and MythTV preinstalled on them, and for a pretty decent price, so I wound up purchasing a Hannibal Duece+ from them.  I got the machine a couple weeks ago, and have had a lot of fun fine-tuning it.  Having a web interface on the box to point your browser at it and view the program schedule and schedule recordings is a kick, too.  The machines are still a little rough around the edges with the initial configuration, but TVEase is showing a lot of promise, with an active forum and a definite open source attitude about how to configure the machines for new customers.  The only current drawback is the deathgrip the cable industry has over the digital channels – trying to get off-the-shelf hardware that supports CableCARD® is a bit of a joke currently.  If you’re in the market for a DVR, and aren’t married to all the high-numbered channels, I’d definitely recommend picking up one of these things.

Does your software interact with Bugzilla?

We’ve had a page up on the wiki for several months now listing things we know about that interact with Bugzilla. With the release of Bugzilla 3.0 imminent, now is a great time to make sure that your cool app that knows how to talk to Bugzilla or does something cool with Bugzilla data is listed there so people can find it. If you know of anything cool that interacts with Bugzilla that isn’t listed there yet, even if you’re not responsible for it, feel free to add it to the list.

Bugzilla 3.0 release candidates in the works

The Bugzilla QA guys just signed off on the 3.0rc1 release, which means now it’s time to actually push that release out the door.  As mentioned in my last post, we need volunteers to help us stage the website updates and so forth, and the job is even bigger this time because this is a major new version instead of just a bugfix update.  Bug 370704 has the list of what still needs to be done.  Any help anyone can provide with the website updates and updating documentation would be greatly appreciated.

Bugzilla Releases

In the last couple days, we’ve released versions 2.22.2, 2.20.4, and 2.23.4 of Bugzilla.

Version 2.22.2 is our current “stable” version. We’ve been intending to release this update to the 2.22 series for the last three months or so because it fixes compatibility issues with new versions of MySQL 5 and Template Toolkit 2.15. Those of us that deal with the actual mechanics of making a release happen (all on a volunteer basis) have had other things happening in real life keeping us from working on making it happen for the last few months. The issue got forced in the last couple weeks because of the discovery of a cross-site scripting vulnerability in the Atom feeds. Still, even with a fix for the security bug available the same day the bug was reported, it took us 12 days to release. This really isn’t fair to our users, and it certainly caused us enough strife with people who knew about it complaining about “when are we going to release?”

The process of getting a release pushed out the door (documented here) usually takes about 2 full days (with time off to sleep in the middle) for a single person to complete. It’s a lot of work. Max says he once managed to pull it off in 6 hours, but that’s probably an exception more than the rule. We all have “real jobs” other than working on Bugzilla, which makes even that a difficult chunk of time to be able to commit. We have found in the past that getting 2 or 3 people to work on it together (at the same time mind you, so they can coordinate), it can be pulled off in 3 to 5 hours. But we didn’t seem to find 2 or 3 people who could be in the same place at the same time to do it this time. This is all kind of a roundabout way of saying “we need help!” 🙂 If you look at the documentation link I provided above, the primary stuff we need help with is the pre-release section and the web site updates. Most of the stuff from there down on the list doesn’t take long, and can be done by the acting release manager in an hour or two.

Now that I have a working blog again, I’m going to make use of it and post here looking for volunteers the next time we’re ready to move on a release. 🙂 Our next release, barring any new security issues being discovered, will be a release candidate for version 3.0, but based on the remaining blockers in the buglist, it’s probably a month or two off yet.

The exam is done

So I think the exam went pretty well.  I know I passed the first half, I’ll get the results of the second half and the overall sometime in the next three business days.  Now I have to get out of here in a hurry to try to get home ahead of the incoming storm at home.  It’s likely I’ll be driving at least part of the way through the middle of a blizzard.  Originally I was planning on staying here another day (I’m in Chicago for the class), and heading home tomorrow, but the weather forecast looks like if I don’t go now I’ll be stuck here until Tuesday or so.

The class and the exam were a lot of fun.  Lots of challenging problems and it was a lot of fun to fix them up. 🙂 I did learn enough new tricks from the class part to have made it well worth my while taking the class.  I’d highly recommend it to anyone with good Linux experience that’s interested.  Just make sure you have an employer willing to pay for it because it’s expensive. 🙂