summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorgerv%gerv.net <>2002-05-02 08:10:21 +0200
committergerv%gerv.net <>2002-05-02 08:10:21 +0200
commitbb9af2947de0152ef2a412aabf49dc7b487d5bd7 (patch)
tree0c1f95b21cc7607f3971445e61274c341b4bb0db
parent67e375cb7efdaa3946ec3631766f9b249124ccdc (diff)
downloadbugzilla-bb9af2947de0152ef2a412aabf49dc7b487d5bd7.tar.gz
bugzilla-bb9af2947de0152ef2a412aabf49dc7b487d5bd7.tar.xz
ug 105877 - Backup & check for modifications before upgrade.
-rw-r--r--docs/sgml/installation.sgml20
-rw-r--r--docs/xml/installation.xml20
2 files changed, 30 insertions, 10 deletions
diff --git a/docs/sgml/installation.sgml b/docs/sgml/installation.sgml
index 2697bb391..0a68c250f 100644
--- a/docs/sgml/installation.sgml
+++ b/docs/sgml/installation.sgml
@@ -1173,11 +1173,21 @@ bash# ./checksetup.pl
<section>
<title>Upgrading From Previous Versions</title>
<para>
- 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 <filename>cvs -z3
+ update</filename>, and resolve conflicts if there are any.
+ </para>
+ <para>
+ 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.
</para>
<para>
If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
diff --git a/docs/xml/installation.xml b/docs/xml/installation.xml
index 2697bb391..0a68c250f 100644
--- a/docs/xml/installation.xml
+++ b/docs/xml/installation.xml
@@ -1173,11 +1173,21 @@ bash# ./checksetup.pl
<section>
<title>Upgrading From Previous Versions</title>
<para>
- 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 <filename>cvs -z3
+ update</filename>, and resolve conflicts if there are any.
+ </para>
+ <para>
+ 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.
</para>
<para>
If you are running Bugzilla version 2.8 or lower, and wish to upgrade to