public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
* Bugzilla upgrade check-list
@ 2010-09-22 22:24 Frédéric Buclin
  0 siblings, 0 replies; only message in thread
From: Frédéric Buclin @ 2010-09-22 22:24 UTC (permalink / raw)
  To: overseers

[-- Attachment #1: Type: text/plain, Size: 108 bytes --]

Here is my check-list for the GCC Bugzilla upgrade tomorrow. May be
useful for future upgrades.

Frédéric

[-- Attachment #2: bugzilla_checklist.txt --]
[-- Type: text/plain, Size: 2617 bytes --]

HOW-TO: UPGRADE BUGZILLA FROM 2.20 to 3.6.x
===========================================

Pre-upgrade
-----------
1. Run sanitycheck.cgi from 2.20. Make sure there are no errors besides the invalid
   email address ones (currently, bug 45728 should have everconfirmed = 1).
2. Set the shutdownhtml parameter to "<p>GCC Bugzilla is down for maintainance.
   Downtime: 3 hours (18:00 - 21:00 GMT)</p>".
3. Backup the DB: mysqldump -u root -p bugs > ~/bugs_backup_20100923.sql
4. Delete the localconfig file and the data/ repository from the *test* (3.6.2)
   installation, i.e. bugzilla-test/localconfig and bugzilla-test/data/.
5. Copy the localconfig file and data/ repository from the 2.20 installation
   into the 3.6.2 one. 3.6.2 will now point to the production DB.
6. Rename the production bugzilla/ repository to e.g. bugzilla-old/.
   Then rename bugzilla-test/ to bugzilla/, so that Apache points to it.

Upgrade
-------
1. Run checksetup.pl once. It will stop quickly, because there are some new parameters
   in localconfig. No need to edit them; the defaults are fine.
2. Run checksetup.pl again. It's going to upgrade the DB for real (InnoDB, new defaults,
   etc...). It's going to take a while.
3. Once the upgrade completed, run contrib/recode.pl to convert the DB to UTF8:
   contrib/recode.pl --guess --show-failures --charset=cp1252
4. Turn on the utf8 parameter (by accessing editparams.cgi directly, because all other
   pages are unavailable due to the shutdown). Bugzilla will ask you to run checksetup.pl
   again to finalize the move to UTF8.
5. Run checksetup.pl for the 3rd (and last) time. Now it will focus on converting the DB
   to UTF8.

Post-upgrade
------------
1. Turn on the allow_attachment_display parameter.
2. Set mail_delivery_method to "SMTP".
3. Clear the shutdownhtml parameter. We need to access other admin pages.
4. Only allow UNCONFIRMED for new bugs.
5. Set "disable bugmail" to true for gcc-bugzilla@gcc.gnu.org.
6. Disable the gcc-bugs@gcc.gnu.org, java-prs@gcc.gnu.org and bug-classpath@gnu.org user
   accounts. They should only get bugmail.
7. For all 3 mailing-lists above, use sudo to fix email settings: no email should be
   sent for keyword changes and "other" changes only.
8. Run sanitycheck.cgi again, to make sure no new errors are being detected.

Post-upgrade (outside Bugzilla)
-------------------------------
1. Fix the Subjet of commit messages: Bug NNN must become [Bug NNN].
2. Incoming emails must be redirected to bugzilla/email_in.pl.

Wishlist
--------
- Only members of the reconfirmers group can edit the reconfirmed_on field. (still wanted?)

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-09-22 22:24 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-22 22:24 Bugzilla upgrade check-list Frédéric Buclin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).