From: gerv%gerv.net <> Date: Fri, 4 Apr 2008 11:46:07 +0000 (+0000) Subject: ug 105877 - Backup & check for modifications before upgrade. X-Git-Tag: bugzilla-3.1.3~234 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6dd25ae0f30dcd0a6ea537c9ad688c8b03760a80;p=thirdparty%2Fbugzilla.git ug 105877 - Backup & check for modifications before upgrade. --- diff --git a/docs/en/xml/installation.xml b/docs/en/xml/installation.xml index 2697bb391c..0a68c250f9 100644 --- a/docs/en/xml/installation.xml +++ b/docs/en/xml/installation.xml @@ -1173,11 +1173,21 @@ bash# ./checksetup.pl
Upgrading From Previous Versions - The developers of Bugzilla are constantly adding new tables, columns and - fields. You'll get SQL errors if you just update the code. The strategy - to update is to simply always run the checksetup.pl script whenever - you upgrade your installation of Bugzilla. If you want to see what has - changed, you can read the comments in that file, starting from the end. + A plain Bugzilla is fairly easy to upgrade from one version to a newer one. + However, things get a bit more complicated if you've made changes to + Bugzilla's code. In this case, you may have to re-make or reapply those + changes. + It is recommended that you take a backup of your database and your entire + Bugzilla installation before attempting an upgrade. You can upgrade a 'clean' + installation by untarring a new tarball over the old installation. If you + are upgrading from 2.12 or later, you can type cvs -z3 + update, and resolve conflicts if there are any. + + + Because the developers of Bugzilla are constantly adding new tables, columns + and fields, you'll probably get SQL errors if you just update the code and + attempt to use Bugzilla. Always run the checksetup.pl script whenever + you upgrade your installation. If you are running Bugzilla version 2.8 or lower, and wish to upgrade to