All users were logged out of Bugzilla on October 13th, 2018

2.12 Release Tracking Bug

VERIFIED FIXED in Bugzilla 2.12



18 years ago
6 years ago


(Reporter: CodeMachine, Assigned: tara)


Bugzilla 2.12
Dependency tree / graph





18 years ago
This bug is for tracking the release of 2.12.  At least the following needs to
be done:

1.  All bugs closed.
2.  Maybe run on b.m.o for a couple of days?
3.  Release announcement written.
4.  Work out where to send release announcement ( front page/webtools
newsgroup/where else?)
5.  Make a branch for 2.12?
6.  Stamp released version with v2.12.
7.  Stamp CVS HEAD with v2.13.
8.  Whatever is necessary to post the tarball on

Please include anything else that needs to be done, as well as comments about
the progress of the release.


18 years ago
Depends on: 73181
Target Milestone: --- → Bugzilla 2.12
addding CC

Comment 2

18 years ago
Well break an egg and call it art!  Apparently we have a web page at
"".  This will need an update for 2.12
too.  Not sure if all the addresses are still valid after the Blue Martini
shakeup but you can add mine in there if you're short of them.  =)

Henrik, please don't add comments that don't do anything to explain your
change.  They don't achieve anything, and you're causing people to receive
notifications who have elected to receive comments but not CC changes.

Comment 3

18 years ago
We should put the 2.12 Release Notes on the web page as well, once we've

Comment 4

18 years ago
Adding bugs with 2.12 milestone.
Depends on: 72721, 76261, 76524

Comment 5

18 years ago
Adding dependencies on bugs with this milestone is not a good idea because they
can be dropped off the radar, and I intend a release tracking bug to be a
permanent practice throughout the cycle of 2.14, so it will be impractical and
of little benefit to track things this way.

Comment 6

18 years ago
I am not sure I understand.  The purpose of adding them to this bug was to put
them ON the radar.

Comment 7

18 years ago
They are already on the radar, I would rather not have a second copy of that
information.  I don't want to have to edit long lists of dependencies if and
when they do drop off.

Comment 8

18 years ago
It's already possible with a simple query to see all open bugs targeted for 2.12
(or any other milestone, for that matter).  Having to manage an extra dependany
list for the same thing is sub-optimal.

Comment 9

18 years ago
I realize that.  Can I get mail whenever a 2.12 bug is changed or added?

Comment 10

18 years ago
Nah, but a periodic query isn't too inconvenient, at least when we're down to
this few bugs (which is the only time we could feasibly do the dependencies
thing anyway).

Adding this sort of functionality comes under the banner of bug #14137.

Comment 11

18 years ago
It's looking like tommorowish, assuming Barnboy gets bug #76156 done as he says.

Dave, hope you've got the web page update for 2.12 ready.
I'll drop into IRC sometime tonight and work on it and get suggestions.  I'm busy 
at work at the moment.

Comment 13

18 years ago
Is step "3.  Release announcement written." done yet?
  Will there be a short version for and a 
  longer one for the newsgroup/project page?

And for "5.  Make a branch for 2.12?" is it gonna be branched or just tagged?

I assume the same person will do 6, 8a, and 7...
  And what is neccessary for 8b?

8a being actually making the tarball
8b being posting the tarball at 

Comment 14

18 years ago
We're finally SHIPPING this mother!

Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 15

18 years ago
Bug #77548 is the 2.14 release tracking bug.

Comment 16

18 years ago
tag: BUGZILLA-2_12
tarball: bugzilla-2.12.tar.gzcvs l

Comment 17

18 years ago
That should be just tarball bugzilla-2.12.tar.gz but it won't be there until
Dawn puts it there.

Comment 18

18 years ago
Moving closed bugs to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.