We are freezing for Bugzilla 3.4 in exactly two months. So, sometime in the next two weeks, I want to release a 3.3.1 development release, so people have enough time to give feedback before we freeze. I want to do this regardless of whether there's a 3.2.1 or 3.0.7 to release.
Okay, thanks to almost all the sec bugs being ready, we're going to expand this into several releases.
Summary: Release Bugzilla 3.3.1 → Release Bugzilla 3.3.1, 3.2.1, 3.0.7, and 2.22.7
For anybody interested, I plan to do this release between Tuesday and Friday of this week.
Yes, we postpone them all. As long as we don't know what the problem is, it doesn't make sense to block releases for something which is not reproducible.
Because justdave wants a fix for bug 472206 before we release 3.2.1, we need to release a 3.3.1 before we do all this (because we urgently need a development release, since we freeze on Jan 29).
Summary: Release Bugzilla 3.3.1, 3.2.1, 3.0.7, and 2.22.7 → Release Bugzilla 3.3.2, 3.2.1, 3.0.7, and 2.22.7
This release is going to happen on Monday. We don't want to spring a major security update on sysadmins on Friday. Everything is pretty much ready for the release though, so it shouldn't be any problem to do it Monday.
Okay, all the security patches have been checked in. We just have to wait now for all the tinderboxen to pass, and then we can start the release process.
Status: NEW → ASSIGNED
Okay, I'm starting the release process now.
I've bumped all the version numbers.
Tarballs rolled and posted.
Created attachment 360185 [details] [diff] [review] Monolithic Website Patch Here's the web site updates that I'm about to check in.
Assignee: general → mkanat
Okay, website updates checked in. Now we just have to wait for the site to rebuild itself, and then kick the Netscaler.
Okay, FreshMeat updated, LpSolit updated bugzilla-update.xml, I sent out all the announcements and the advisory, and now we're all done.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.