summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjake%bugzilla.org <>2003-07-01 03:51:59 +0200
committerjake%bugzilla.org <>2003-07-01 03:51:59 +0200
commit1c383fd4d2c38b6ce3d787d20b6600359c62f24b (patch)
tree5d0788c0364e2b5368887f48e18681f96b7f489c
parentd34ef69ff48200d3f6e6f0925d803675a32bb5ab (diff)
downloadbugzilla-1c383fd4d2c38b6ce3d787d20b6600359c62f24b.tar.gz
bugzilla-1c383fd4d2c38b6ce3d787d20b6600359c62f24b.tar.xz
Bug 206498 - Add a warning that Bugzilla upgrades are irreversable and that backups should be made.
-rw-r--r--docs/xml/administration.xml8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/xml/administration.xml b/docs/xml/administration.xml
index ecf465fdc..a57001638 100644
--- a/docs/xml/administration.xml
+++ b/docs/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.