The list of blockers is pretty small now and the remaining blockers should be fixed soon: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=flag%3Ablocking3.2%2B Also, QA is doing some progress and we can expect some new Selenium tests in the near future; see progress at: http://landfill.bugzilla.org/bugzillaqa/showdependencygraph.cgi?id=3065 and: http://landfill.bugzilla.org/bugzillaqa/showdependencygraph.cgi?id=3130 We have a security bug ready for checkin (bug 449931), which affects all supported branches, so we also have to release 3.0.6, 2.22.6 and 2.20.7. Per my last discussion with mkanat, he doesn't plan to release 3.3.1 yet, which will let us focus on 3.2 final.

All blockers are ready for checkin, so I'm going to start work on this.

Comment on attachment 346496 [details] [diff] [review] v1 Wrong bug.

FYI, all our current Selenium + (updated) Webservice scripts pass successfully with MySQL. Didn't test with PostgreSQL yet. I will test tomorrow.

(In reply to comment #4) > Didn't test with PostgreSQL yet. I will test tomorrow. Bah, Pg is broken on my system (maybe related to a recent kernel update). I will let manu confirm that all scripts pass successfully with Pg.

You can see all current patches at the staging site in the URL field.

Bumping version numbers for releases: 2.20: Checking in Bugzilla/Config.pm; /cvsroot/mozilla/webtools/bugzilla/Bugzilla/Config.pm,v <-- Config.pm new revision: 1.43.2.18; previous revision: 1.43.2.17 done Checking in docs/xml/Bugzilla-Guide.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/Attic/Bugzilla-Guide.xml,v <-- Bugzilla-Guide.xml new revision: 1.50.2.13; previous revision: 1.50.2.12 done 2.22: Checking in Bugzilla/Config.pm; /cvsroot/mozilla/webtools/bugzilla/Bugzilla/Config.pm,v <-- Config.pm new revision: 1.51.2.16; previous revision: 1.51.2.15 done Checking in docs/xml/Bugzilla-Guide.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/Attic/Bugzilla-Guide.xml,v <-- Bugzilla-Guide.xml new revision: 1.57.2.11; previous revision: 1.57.2.10 done 3.0: Checking in Bugzilla/Constants.pm; /cvsroot/mozilla/webtools/bugzilla/Bugzilla/Constants.pm,v <-- Constants.pm new revision: 1.68.2.18; previous revision: 1.68.2.17 done Checking in docs/xml/Bugzilla-Guide.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/Attic/Bugzilla-Guide.xml,v <-- Bugzilla-Guide.xml new revision: 1.71.2.9; previous revision: 1.71.2.8 done 3.2: Checking in Bugzilla/Constants.pm; /cvsroot/mozilla/webtools/bugzilla/Bugzilla/Constants.pm,v <-- Constants.pm new revision: 1.92.2.5; previous revision: 1.92.2.4 done Checking in docs/en/xml/Bugzilla-Guide.xml; /cvsroot/mozilla/webtools/bugzilla/docs/en/xml/Bugzilla-Guide.xml,v <-- Bugzilla-Guide.xml new revision: 1.78.2.3; previous revision: 1.78.2.2 done

All releases tagged.

I'm going away for a few hours, I'll tarball and upload the releases when I get back.

All releases tarballed, uploaded, and synced, so we're ready to go, pretty much.

Here's all the website updates that will be happening, as one patch.

Website updates checked in, waiting for them to sync and then I'll be sending out emails.

Website has updated. I've bumped all the version numbers post-release.

Okay, everything is done. I've sent out all the announcements and updated Freshmeat. LpSolit still needs to update bugzilla-update.xml.

(In reply to comment #7) > Bumping version numbers for releases: pages/release-notes.html.tmpl still says: | title = "$terms.Bugzilla 3.0.5 Release Notes" Worth filing such a trivial bug?

(In reply to comment #15) > Worth filing such a trivial bug? Yes, actually. We should just make it say the current version number.