Bommels05/Mozilla
Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ug 105877 - Backup & check for modifications before upgrade.

Browse Source 
git-svn-id: svn://10.0.0.236/trunk@120483 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
gerv%gerv.net 2002-05-01 23:10:21 +00:00
parent 7a6440b27a
commit 571ee6fa5b
2 changed files with 30 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
mozilla/webtools/bugzilla/docs/sgml/installation.sgml
View File

@ -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

20
mozilla/webtools/bugzilla/docs/xml/installation.xml
View File

@ -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