Closed
Bug 280371
(bmo-upgrade-051022)
Opened 19 years ago
Closed 18 years ago
upgrade bugzilla.mozilla.org to 2.20
Categories
(bugzilla.mozilla.org :: General, defect, P1)
bugzilla.mozilla.org
General
Tracking
()
RESOLVED
FIXED
People
(Reporter: justdave, Assigned: justdave)
References
()
Details
(Whiteboard: Completed Saturday, October 22rd, 2005 at 9pm PDT)
This is a metabug for tracking our next upgrade of bugzilla.mozilla.org. For reference, our last upgrade was tracked on bug 244831.
Assignee | ||
Comment 1•19 years ago
|
||
I'm planning to do this upgrade at some point in the next week or so, I'll set an exact date once I have a better assessment of the amount of preliminary work that will be required. We need to do this to pick up several of the bugfixes corrected upstream as a result of our last upgrade, as well as to deploy some additional local changes that have been in the works for a while.
Alias: bmo-upgrade
Whiteboard: planning to do this within the next week or so - no date set yet
Assignee | ||
Comment 2•19 years ago
|
||
Too many other sysadmin things have come up for me to get very far with this yet, and with the other stuff that's still on the list, this is likely still more than a week off yet. For the record, I will not be updating to cvs-tip this next time... there's been a lot of potentially destabilizing architectural changes to Bugzilla recently, and they need time to bake before they go on a production site. I will probably upgrade to 2.19.2 or somewhere shortly thereafter in CVS.
Assignee | ||
Updated•19 years ago
|
Priority: -- → P3
Whiteboard: planning to do this within the next week or so - no date set yet → planning to do this within the next month or so - no date set yet
Assignee | ||
Comment 3•19 years ago
|
||
Current plan is to upgrade to the tip of the 2.20 branch. This is in line after the restructuring of the addons.mozilla.org back-end infrastructure, so it's probably still a week or two off, at a minimum.
Assignee | ||
Updated•19 years ago
|
Severity: normal → critical
Priority: P3 → P1
Whiteboard: planning to do this within the next month or so - no date set yet → TENTATIVE date Sunday Aug 14, subject to change if I don't finalize it by tonight.
Assignee | ||
Comment 4•19 years ago
|
||
We had a situation last night with email that demanded my attention for several hours, and I didn't get to do the preliminary work yet that I need to do to know what kind of schedule impact this will have. I'm within a few hours of having that work ready, however, we've lost our window for adequate advance warning of the upgrade, and I'd really prefer a little more time to test it before deploying, too. If I get the preliminaries done and it turns out the upgrade will take less than 2 hours, I might do it during off-peak hours during the week. If it'll take longer, it'll have to wait until next weekend. I'll have an update in the next day or so.
Whiteboard: TENTATIVE date Sunday Aug 14, subject to change if I don't finalize it by tonight. → TENTATIVELY within the next week
Assignee | ||
Comment 5•19 years ago
|
||
There's too much on the agenda (and too little sysadmin staff) to prepare for Firefox 1.5 to get to this in the immediate future. The soonest we'll be able to get to this is October 9th.
Whiteboard: TENTATIVELY within the next week → tentatively scheduled for Sunday, October 9th, 2005 at 6pm PDT
Assignee | ||
Comment 6•19 years ago
|
||
OK, most of the preliminary work on the upgrade is done, however, we need some playtime with the test install, and I want a week to have it announced at the top of b.m.o ahead of time (I'll put the banner up on Monday). Given the lack of regression bugs filed since Bugzilla 2.20 was publicly released 2 weeks ago (there haven't been any at all yet, first time in as long as I can remember that that's happened -- first time we've had a real pre-release QA plan, too, so I guess it helped), I have increasing confidence in the stability of this version, and think we can still get this in ahead of the Firefox 1.5 RC releases without causing any undo stress on the build/qa folks.
Whiteboard: tentatively scheduled for Sunday, October 9th, 2005 at 6pm PDT → Scheduled for Sunday, October 23rd, 2005 at 6pm PDT, duration ~3 hours
Assignee | ||
Comment 7•19 years ago
|
||
Moving the schedule up one day to avoid a conflict with the Firefox 1.5 RC1 freeze.
Whiteboard: Scheduled for Sunday, October 23rd, 2005 at 6pm PDT, duration ~3 hours → Scheduled for Saturday, October 22rd, 2005 at 6pm PDT, duration ~3 hours
Assignee | ||
Comment 8•19 years ago
|
||
The upggrade itself is done. Leaving this open for now to track a few followup issues. Regressions are being tracked on bug 313429
Whiteboard: Scheduled for Saturday, October 22rd, 2005 at 6pm PDT, duration ~3 hours → Copmleted for Saturday, October 22rd, 2005 at 9pm PDT
Assignee | ||
Updated•19 years ago
|
Whiteboard: Copmleted for Saturday, October 22rd, 2005 at 9pm PDT → Completed Saturday, October 22rd, 2005 at 9pm PDT
Assignee | ||
Updated•18 years ago
|
Alias: bmo-upgrade → bmo-upgrade-051022
Assignee | ||
Updated•18 years ago
|
Assignee: justdave → justdave
Assignee | ||
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Summary: bugzilla.mozilla.org upgrade meta-bug → upgrade bugzilla.mozilla.org to 2.20
Updated•13 years ago
|
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•