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)

defect

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.
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
Depends on: 234142
Depends on: 279823
Depends on: 276503
Depends on: 280092
Depends on: 274365
Depends on: 250400
Depends on: 275064
Depends on: 281881
Depends on: 277215
Depends on: 276487
Depends on: 170440
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.
Depends on: 181371
Depends on: 270999
Depends on: 150901
No longer depends on: 150901
Depends on: 285986
Depends on: 274582
Depends on: 277568
Depends on: 274191
Depends on: 275868
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
Depends on: 272140
Depends on: 288333
Depends on: 165825
Depends on: 183758
Depends on: 181684
Blocks: 232232
Depends on: 148554
Blocks: 293505
Depends on: 296145
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.
Depends on: 304149
Blocks: 304356
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.
No longer blocks: 304356
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
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
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
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
Depends on: 313098
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
Depends on: 313579
Depends on: 313910
Whiteboard: Copmleted for Saturday, October 22rd, 2005 at 9pm PDT → Completed Saturday, October 22rd, 2005 at 9pm PDT
Depends on: 313816
Alias: bmo-upgrade → bmo-upgrade-051022
Assignee: justdave → justdave
No longer depends on: 285986
No longer depends on: 277568
No longer depends on: 313816
No longer depends on: 272140
No longer depends on: 288333
No longer depends on: 304149
No longer depends on: 313910
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Summary: bugzilla.mozilla.org upgrade meta-bug → upgrade bugzilla.mozilla.org to 2.20
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.