Closed
Bug 306901
(bz-220)
Opened 20 years ago
Closed 20 years ago
Release of Bugzilla 2.18.4, 2.20, and 2.21.1
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mkanat, Assigned: mkanat)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
1.16 KB,
patch
|
Details | Diff | Splinter Review | |
1.22 KB,
patch
|
Details | Diff | Splinter Review | |
1.23 KB,
patch
|
Details | Diff | Splinter Review | |
114.45 KB,
patch
|
Details | Diff | Splinter Review |
2.20 hasn't yet had a chance to get wide-scale testing on bugzilla.mozilla.org,
but we've had a fairly long release-candidate cycle, with a lot of people
downloading 2.20rc2.
So, I think 2.20 is stable enough to release. It seems to be working quite well
for many people who have downloaded it (I've been watching the mozilla-webtools
lists).
We will also release our first development release of 2.21.
Assignee | ||
Updated•20 years ago
|
Alias: bz-220
Assignee: general → mkanat
![]() |
||
Comment 1•20 years ago
|
||
mkanat, there is one blocker left for 2.20, with a patch awaiting review. The QA
team hopes to start testing today or tomorrow (preferably with the blocker
reviewed and checked in). I suggest that you already start fixing the blockers
of this bug so that we can release 2.20 as soon as the QA team is ready.
Assignee | ||
Comment 2•20 years ago
|
||
We are now also releasing 2.18.4, because of a Security Advisory that will have
to go with it.
Summary: Release of Bugzilla 2.20 and 2.21.1 → Release of Bugzilla 2.18.4, 2.20, and 2.21.1
Assignee | ||
Comment 4•20 years ago
|
||
Versioning changes for the tip.
Assignee | ||
Comment 5•20 years ago
|
||
Assignee | ||
Comment 6•20 years ago
|
||
Assignee | ||
Comment 7•20 years ago
|
||
Versioning complete:
tip:
Checking in Bugzilla/Config.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Config.pm,v <-- Config.pm
new revision: 1.47; previous revision: 1.46
done
Checking in docs/xml/Bugzilla-Guide.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/Bugzilla-Guide.xml,v <--
Bugzilla-Guide.xml
new revision: 1.55; previous revision: 1.54
done
2.20:
Checking in Bugzilla/Config.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Config.pm,v <-- Config.pm
new revision: 1.43.2.4; previous revision: 1.43.2.3
done
Checking in docs/xml/Bugzilla-Guide.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/Bugzilla-Guide.xml,v <--
Bugzilla-Guide.xml
new revision: 1.50.2.4; previous revision: 1.50.2.3
done
2.18:
Checking in Bugzilla/Config.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Config.pm,v <-- Config.pm
new revision: 1.21.2.9; previous revision: 1.21.2.8
done
Checking in docs/xml/Bugzilla-Guide.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/Bugzilla-Guide.xml,v <--
Bugzilla-Guide.xml
new revision: 1.37.2.13; previous revision: 1.37.2.12
done
Assignee | ||
Comment 8•20 years ago
|
||
Releases tagged. Now just waiting for the tags to propagate to cvs-mirror so
that I can roll the tarballs.
Assignee | ||
Comment 9•20 years ago
|
||
OK, tarballs posted, now we wait for them to propagate to mirrors. We happen to
be undergoing the MoFo "hour of terror" at the moment (where all Firefox 1.0
installs check-in about their update all at once), but hopefully that shouldn't
affect this too badly.
Assignee | ||
Comment 10•20 years ago
|
||
Here's all the web updates that I'm about to post, in one huge patch.
Assignee | ||
Comment 11•20 years ago
|
||
OK, we had a little snag there. We discovered a regression from one of the
security bugs, which caused config.cgi to not work in perl 5.6.1. We've fixed
it, and I've re-posted the tarballs with the fix. Now we just need to wait for
the mirrors to pick up the tarballs, and then I can announce the release.
Assignee | ||
Comment 12•20 years ago
|
||
OK, release is complete. Post-release stuff like updating the version trackers
still has to be done.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•