[Dev] Bugzilla upgrade

[Mike Taylor]

Jefferson, the IT intern, has completed all of the test runs and plans 
for the upgrade of our Bugzilla to the latest version.

He has asked that this upgrade happen tomorrow evening - Friday, Feb 
3rd 2006.

The upgrade will involve the following steps:

1. Disable the vhost in apache to avoid any possible races.
2. Backup the DB.
3. Move the symlinks and adjust the config for 2.20 to point to the 
live DB.
4. Run the check scripts for each of bugzilla and testrunner which will 
do
the necessary upgrades for the new versions.
5. Re-enable the vhost in apache and confirm things look right.

During the time of the upgrade Bugzilla will be offline.

Is the timing going to cause anyone any serious issues?  Please respond 
by tomorrow morning if you have any concerns.

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
http://www.osafoundation.org

bear at code-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20060202/71e2289c/PGP.pgp