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.
Wow, that was fast. They said they’d have the results of the RHCE exam posted sometime in the next 3 business days (which would mean sometime next week), but I had an email waiting for me when I got home tonight with the results. I passed. So I’m now officially a Red Hat Certified Engineer.
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. 🙂
I’m taking the RHCE exam today. Based on the last four days of RH300 classes (which have been awesomely fun) this should be a blast. I love fixing things so even if I don’t pass I think it will be great fun taking the exam.
None of the official mentions of getting support for Bugzilla say to mail me. They all point at newsgroups or mailing lists. But every so often, someone decides to mail me directly anyway, probably because they found my email address on the header of a source file or something listed as a contributor, or off the project history page or something. Sometimes I try to help, most of the time I just refer them back to the support page on the website. Anyhow, the ones I do get are often quite strange. Take this one for example:
I need free bugzilla books, i want to know about bugzilla,.
Send it through mail or particullar site address.
waiting for your reply
So I sent this courteous (I thought) reply:
http://www.bugzilla.org/docs/ is your best bet if you want free. It’s
viewable online or you can download and print the PDF.
All done, right? Not so, I got this back from him:
Thank you, I found it.
It’s contain lot of topics.. I am going to learn this. I am very
interesting to learn this.
Can you please send me the way of studing, that means, what should i
do, what should not i do,
Beacause when i install it, i have faced lot of problems, which is made by me..
Beacause i confused to do..
So, Can you please send me the Crisp Notation of Bugzilla, It should
be Short & Sweet.
With Warm Regards
I don’t know about you, but to me this is an incredibly vague request. That’s like saying “please tell me everything there is to know about the world in 20 words or less.”
I replied pointing him at the support page on the website, and suggesting he ask more-specific questions when he gets there.