480837 - (bz-release-323) Release Bugzilla 3.2.3 and 3.3.4

Status: RESOLVED FIXED

(Bugzilla :: Bugzilla-General, defect)

Description

[Frédéric Buclin]

We are mostly done with bugs blocking 3.3.4 and 3.2.3. All we still need is a backport for 3.0.9 for bug 476603 and that's it. I don't consider bug 376044 as a hard blocker as this problem exists since Bugzilla 3.0. So I think we can release very soon now (maybe next week if mkanat has time for release stuff).

Bugzilla 3.2.3 is much wanted because it fixes the remaining regressions introduced by security bugs, and Bugzilla 3.3.4 is feature-complete (including the new UI for index.cgi) so it's time to get broader feedback before we start working on 3.4rc1. Bugzilla 3.0.9 will only contain the security fix.

Comment 1

[Frédéric Buclin]

OK, we just realized that the security fix cannot land on the 3.0 branch because we don't store all the required information in the DB. As there is no other checkin on that branch, there is no need to release 3.0.9. So this will be a 3.3.4 + 3.2.3 release only.

Comment 3

[Max Kanat-Alexander]

Okay, we're ready to do the release, so we're just going to go ahead with it.

Comment 4

[Max Kanat-Alexander]

Created BUGZILLA-3_4-BRANCH and bumped the version number on it:

Checking in Bugzilla/Constants.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Constants.pm,v  <--  Constants.pm
new revision: 1.109.2.1; previous revision: 1.109
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.83.2.1; previous revision: 1.83
done

Comment 5

[Max Kanat-Alexander]

Okay, I bumped the version number on trunk to 3.5, and then bumped the 3.2 branch to 3.2. Then I used my tagging script to tag the releases. Here's the output from the script:

Dev Release: 3.3.4
Stable Releases: 3.2.3

Tagging Releases...

cvs -Q -d [e-mail]:/cvsroot co -P -d BUGZILLA-3_2-BRANCH -r BUGZILLA-3_2-BRANCH Bugzilla
Checked out BUGZILLA-3_2-BRANCH for 3.2.3.

cvs -Q up -dP -r BUGZILLA-3_2-BRANCH
cvs -Q  tag -FR BUGZILLA-3_2_3
Added the tag BUGZILLA-3_2_3 to BUGZILLA-3_2-BRANCH
cvs -Q up -dP -r BUGZILLA-3_2-STABLE
cvs -Q  tag -R -d BUGZILLA-3_2-STABLE
Removed the BUGZILLA-3_2-STABLE
cvs -Q up -dP -r BUGZILLA-3_2-BRANCH
cvs -Q  tag -FR BUGZILLA-3_2-STABLE
Added the tag BUGZILLA-3_2-STABLE to BUGZILLA-3_2-BRANCH
cvs -Q up -dP -r Bugzilla_Stable
cvs -Q  tag -R -d Bugzilla_Stable
Removed the Bugzilla_Stable
cvs -Q up -dP -r BUGZILLA-3_2-BRANCH
cvs -Q  tag -FR Bugzilla_Stable
Added the tag Bugzilla_Stable to BUGZILLA-3_2-BRANCH

cvs -Q -d [e-mail]:/cvsroot co -P -d BUGZILLA-3_4-BRANCH -r BUGZILLA-3_4-BRANCH Bugzilla
Checked out BUGZILLA-3_4-BRANCH for 3.3.4.

cvs -Q up -dP -r BUGZILLA-3_4-BRANCH
cvs -Q  tag -FR BUGZILLA-3_3_4
Added the tag BUGZILLA-3_3_4 to BUGZILLA-3_4-BRANCH

Created Tags:
$VAR1 = {
          '3.2.3' => [
                       'BUGZILLA-3_2_3',
                       'BUGZILLA-3_2-STABLE',
                       'Bugzilla_Stable'
                     ],
          '3.3.4' => [
                       'BUGZILLA-3_3_4'
                     ]
        };

Comment 6

[Max Kanat-Alexander]

Checksetup tinderbox updated.
Tarballs rolled and posted.

Comment 7

[Max Kanat-Alexander]

Attachment: Monolithic Website Updates

Here are all website updates that I'm about to check in, in one patch.

Comment 8

[Max Kanat-Alexander]

Web site updates checked in.

Comment 9

[Max Kanat-Alexander]

Okay, all announcements sent, updated Freshmeat, bumped version numbers post-release, and I believe LpSolit has updated bugzilla-update.xml. So we are done! :-)