All users were logged out of Bugzilla on October 13th, 2018
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 (mozilla.org 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 mozilla.org. Please include anything else that needs to be done, as well as comments about the progress of the release.
Depends on: 73181
Target Milestone: --- → Bugzilla 2.12
Well break an egg and call it art! Apparently we have a web page at "http://www.mozilla.org/projects/bugzilla/". 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.
We should put the 2.12 Release Notes on the web page as well, once we've released.
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.
I am not sure I understand. The purpose of adding them to this bug was to put them ON the radar.
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.
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.
I realize that. Can I get mail whenever a 2.12 bug is changed or added?
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.
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.
Is step "3. Release announcement written." done yet? Will there be a short version for http://www.mozilla.org/index.html 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 - http://ftp.mozilla.org/pub/webtools/bugzilla-2.12.tar.gz - http://ftp.mozilla.org/pub/webtools/bugzilla-LATEST.tar.gz
We're finally SHIPPING this mother! SEEEEEE YAAAAAAA
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Bug #77548 is the 2.14 release tracking bug.
tag: BUGZILLA-2_12 tarball: bugzilla-2.12.tar.gzcvs l
That should be just tarball bugzilla-2.12.tar.gz but it won't be there until Dawn puts it there.
Status: RESOLVED → VERIFIED
Moving closed bugs to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
You need to log in before you can comment on or make changes to this bug.