Closed
Bug 620037
(bz-release-40rc2)
Opened 14 years ago
Closed 13 years ago
Release Bugzilla 4.0rc2, 3.6.4, 3.4.10, and 3.2.10
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mkanat, Assigned: mkanat)
References
(Blocks 1 open bug, )
Details
Attachments
(2 files, 1 obsolete file)
We have some releases to do, including some security fixes.
Flags: blocking4.0+
Flags: blocking3.6.4+
Flags: blocking3.4.10+
Flags: blocking3.2.10+
Assignee | ||
Updated•13 years ago
|
Alias: bz-release-40rc2
Assignee | ||
Comment 1•13 years ago
|
||
Assignee | ||
Updated•13 years ago
|
Assignee | ||
Comment 2•13 years ago
|
||
Attachment #506309 -
Flags: review?(LpSolit)
Comment 3•13 years ago
|
||
Comment on attachment 506309 [details] Announcement Email, v1 >published along with these releases, and that you update as soon as >possible. Remove the comma. > Bugzilla 4.0rc2 is our second Release Candiate for Bugzilla 4.0. Candidate >This release has received QA testing, and should be considerably more Remove the comma. > As a reminder, once the final Bugzilla 4.0 is released, the Bugzilla "the final Bugzilla 4.0" is weird... >in that series. All installations running 3.2.x are strongly encouraged >to update to 3.6.4 or 4.0rc2. 4.0 (once released) -- or something similar. >It is VERY IMPORTANT to read the Release Notes if you are >upgrading from one major version to another (like 3.4.x to 3.6.x). s/like/such as/ > http://twitter.com/#!/bugzilla http://twitter.com/bugzilla
Assignee | ||
Comment 4•13 years ago
|
||
Thanks! Fixed all of those things.
Attachment #506309 -
Attachment is obsolete: true
Attachment #506313 -
Flags: review?(LpSolit)
Attachment #506309 -
Flags: review?(LpSolit)
Comment 5•13 years ago
|
||
Comment on attachment 506308 [details] [diff] [review] Website Updates, v1 >Index: lib/release-template/news/index.html >+ <li><a href="news/#release40rc2">Release of Bugzilla 3.2.10, 3.4.10, >+ 3.6.4, and 4.0rc2</a> [ 2011 Jan FIXME ]</li> You should remove Bugzilla 3.7.2 from the list. >Index: src/docs/index.html >- <li><strong>Bugzilla 4.0rc1</strong> >+ <li><strong>Bugzilla 4.0rc2</strong> You must also update the list for the drop-down menu in the Search section of the page. >Index: src/news/index.html >+ <p><a href="../releases/4.0/">Bugzilla 4.0rc2</a> is >+ our second Release Candiate for Bugzilla 4.0. This Candidate* >Index: src/releases/4.0/index.html > <li>Final Release: December 13, 2010*</li> Should be February XX, 2011. I will let you choose what XX is. :) > <li><a href="../../download/#v40">Download Bugzilla 4.0rc1</a></li> Should mention 4.0rc2 now. >Index: src/releases/4.0/release-notes.html > <h1>Bugzilla 4.0 Release Notes</h1> > >+ >+ >+<h1>Bugzilla 4.0 Release Notes</h1> No need to duplicate the title of the page. :) r=LpSolit with these comments fixed.
Attachment #506308 -
Flags: review?(LpSolit) → review+
Comment 6•13 years ago
|
||
Comment on attachment 506313 [details]
Announcement Email, v2
Looks good. r=LpSolit
Attachment #506313 -
Flags: review?(LpSolit) → review+
Assignee | ||
Comment 7•13 years ago
|
||
Release in progress, bumping version numbers now.
Assignee | ||
Comment 8•13 years ago
|
||
Version numbers bumped and tagged in bzr. Waiting for CVS sync so that I can tag the releases in CVS.
Assignee | ||
Comment 9•13 years ago
|
||
Created Tags: $VAR1 = { '3.2.10' => [ 'BUGZILLA-3_2_10', 'BUGZILLA-3_2-STABLE' ], '3.4.10' => [ 'BUGZILLA-3_4_10', 'BUGZILLA-3_4-STABLE' ], '4.0rc2' => [ 'BUGZILLA-4_0rc2' ], '3.6.4' => [ 'BUGZILLA-3_6_4', 'BUGZILLA-3_6-STABLE', 'Bugzilla_Stable' ] };
Assignee | ||
Comment 10•13 years ago
|
||
Tarballs rolled and posted.
Assignee | ||
Comment 11•13 years ago
|
||
Website updates checked in, with all of LpSolit's comments fixed.
Comment 12•13 years ago
|
||
bugzilla-update.xml updated.
Assignee | ||
Comment 13•13 years ago
|
||
Version numbers bumped post-release. Release done! Thank you SO MUCH to everybody who helped out with this one, it was quite a monster effort. :-)
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•