Closed
Bug 302446
Opened 19 years ago
Closed 19 years ago
Release of Bugzilla 2.20rc2
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.20
People
(Reporter: mkanat, Assigned: mkanat)
References
(Blocks 1 open bug, )
Details
I plan to release Bugzilla 2.20rc2 and Bugzilla 2.21.1 in a few days.
It's true that 2.21.1 won't be extremely different from 2.20rc2, but it never
hurts to have some additional testing on the development branch.
Assignee | ||
Comment 1•19 years ago
|
||
As far as I'm aware, there are no security advisories, and no reason to release
anything new on the 2.18 branch, correct?
Comment 2•19 years ago
|
||
I see no interest in releasing 2.21.1 now. I won't do any testing on the tip.
Comment 3•19 years ago
|
||
we probably shouldn't divert testing from the release candidates unless we have
a security advisory that affects the trunk
Comment 4•19 years ago
|
||
(In reply to comment #1)
> As far as I'm aware, there are no security advisories, and no reason to release
> anything new on the 2.18 branch, correct?
Correct. Moreover, there has been only 4 checkins on the 2.18 branch since
2.18.3, among which 1 doc bug, 1 trivial and harmless bug and 2 medium to
critical bugs (bug 273767 and bug 282737). So no 2.18.4 required for the moment.
About 2.21.1, I agree with justdave and I did the same comment in IRC. Please
"force" developers to test 2.20rc2 before giving them 2.21.1 to play with.
2.21.1 doesn't need testing for the moment, at least not as much as 2.20rc2
needs, unless you like releasing new versions every week... And there are around
9-10 blockers left to fix for 2.20! If you release 2.21.1 now, nobody will care
about these blockers anymore.
And b.m.o will soon upgrade to 2.20rc2, so with no 2.21.1 release, we are
(almost) sure everybody will be talking about the same version, which will be
very useful to track regressions.
Please update the topic of the dependent bugs as well.
Comment 5•19 years ago
|
||
The meta bug in the URL field should be closed before releasing 2.20rc2.
/qa
Assignee | ||
Comment 6•19 years ago
|
||
OK. For the purpose of not diverting testing, I agree. Only 2.20rc2.
Summary: Release of Bugzilla 2.20rc2 and 2.21.1 → Release of Bugzilla 2.20rc2
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Bugzilla 2.20
Assignee | ||
Comment 7•19 years ago
|
||
OK, I actually checked-in the version number updates and I'm going to tag the
release now.
Checking in Bugzilla/Config.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Config.pm,v <-- Config.pm
new revision: 1.43.2.1; previous revision: 1.43
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.3; previous revision: 1.50.2.2
done
Assignee | ||
Comment 8•19 years ago
|
||
OK, I've updated the web site:
Checking in index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/index.html.tmpl,v <-- index.html.tmpl
new revision: 1.19; previous revision: 1.18
done
Checking in download/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/download/index.html.tmpl,v <--
index.html.tmpl
new revision: 1.34; previous revision: 1.33
done
Checking in news/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/news/index.html.tmpl,v <--
index.html.tmpl
new revision: 1.25; previous revision: 1.24
done
Checking in releases/2.20/index.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/releases/2.20/index.html.tmpl,v <--
index.html.tmpl
new revision: 1.6; previous revision: 1.5
done
Checking in status/changes.html.tmpl;
/cvsroot/mozilla-org/html/projects/bugzilla/status/changes.html.tmpl,v <--
changes.html.tmpl
new revision: 1.12; previous revision: 1.11
done
No longer depends on: 302453
Assignee | ||
Comment 9•19 years ago
|
||
OK, release announcements sent, and FreshMeat has been updated.
You need to log in
before you can comment on or make changes to this bug.
Description
•