Due to bug 725663, we will have to do releases for all supported branches. We prefer to release 4.2rc3 at the same time as other releases, and then release 4.2 alone in one week.

(In reply to Frédéric Buclin from comment #0) > Due to bug 725663, we will have to do releases for all supported branches. It appeared that only 4.0.2 and newer are affected. No need to release 3.x.

Due to what I said above in comment 1, we will go to 4.2 final directly. No need for a rc3.

Comment on attachment 599329 [details] [diff] [review] website updates (v1) >Index: lib/releases-list.txt >+4.2 2012/02/21 current >+4.0.5 2012/02/21 old Extra space for the 4.2 line, after the tab. >Index: src/index.html >+ <li><a href="news/#release405">Release of Bugzilla 4.2 and 4.0.5</a> The link must be #release42, not #release405. >Index: src/news/index.html >+<h2 id="release42">[ 2012 Feb 21 ] >+ Release of Bugzilla 4.2 and 4.0.5</h2> The title mentions 4.0.5, but there is no paragraph talking about it. >Index: src/releases/4.2/release-notes.html >+<h3>4.0.5</h3> You must not add relnotes for 4.0.3 - 4.0.5 in the relnotes for 4.2. We branched after 4.0.2, which is why we branched in the relnotes there too. >Index: src/status/changes.html >+<tr><td></td></tr> You must add this empty cell to *all* columns, including the older ones which have no new releases, else you totally break the UI, see arrows in http://www-stage.bugzilla.org/status/changes.html >+<tr><td><a href="[% PROCESS query_bzr rev = 8030 %]">4.2rc2 &rarr; 4.2</a></td></tr> The rev ID is wrong as you still has to commit the security bug and bump the version ID. >+<tr><td><a href="[% PROCESS query f='2012-01-31+10:00' t='2012-02-21+10:00' %]">4.0.4 &rarr; 4.0.5</a></td></tr> Here too, it's a bit premature to set the time, or at least you will have to fix once you know when will happen the version bump. Everything else looks good.

All fixed except for dates and rev ids which I will fix on checkin. dkl

Comment on attachment 599402 [details] [diff] [review] website updates (v2) r=LpSolit

Glob, if you review this I can go ahead and start the release process earlier. If not, LpSolit can look at it when he gets back on later. Thanks dkl

Comment on attachment 599470 [details] release announcement (v1) >the next major version of Bugzilla: 4.2! It has been almost a year since You can remove "almost". We released 4.0 exactly one year ago. :) > Bugzilla 4.2 is our best release yet, and we hope that you enjoy >and appreciate the results of thisp past year of hard work by our s/thisp/this/ Everything else looks good. r=LpSolit with these comments fixed.

> Today the Bugzilla Project is pround to announce the release of * proud

Security Advisory sent, bugzilla-update.xml updated.

Website updated and release announcement sent. Versions bumped post release. Thanks for everything! Closing...