summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjake%bugzilla.org <>2008-04-04 13:47:19 +0200
committerjake%bugzilla.org <>2008-04-04 13:47:19 +0200
commit30c184cc956128fec255272bca42714abf7c4f1f (patch)
treee2fd58c82c923e5efba308faf8738d008026c9d5
parentbb005ff9762f696505d3a6e2d0fdf062fd709c19 (diff)
downloadbugzilla-30c184cc956128fec255272bca42714abf7c4f1f.tar.gz
bugzilla-30c184cc956128fec255272bca42714abf7c4f1f.tar.xz
Bug 206498 - Add a warning that Bugzilla upgrades are irreversable and that backups should be made.
-rw-r--r--docs/en/xml/administration.xml8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/en/xml/administration.xml b/docs/en/xml/administration.xml
index ecf465fdc..a57001638 100644
--- a/docs/en/xml/administration.xml
+++ b/docs/en/xml/administration.xml
@@ -1420,6 +1420,14 @@ skip-networking
<section id="upgrading">
<title>Upgrading to New Releases</title>
+ <warning>
+ <para>Upgrading is a one-way process. You should backup your database
+ and current Bugzilla directory before attempting the upgrade. If you wish
+ to revert to the old Bugzilla version for any reason, you will have to
+ restore from these backups.
+ </para>
+ </warning>
+
<para>Upgrading Bugzilla is something we all want to do from time to time,
be it to get new features or pick up the latest security fix. How easy
it is to update depends on a few factors.