summaryrefslogtreecommitdiffstats
path: root/docs/html/upgrading.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/html/upgrading.html')
-rw-r--r--docs/html/upgrading.html30
1 files changed, 30 insertions, 0 deletions
diff --git a/docs/html/upgrading.html b/docs/html/upgrading.html
index f59442061..c3890698f 100644
--- a/docs/html/upgrading.html
+++ b/docs/html/upgrading.html
@@ -76,6 +76,36 @@ CLASS="section"
NAME="upgrading"
></A
>5.9. Upgrading to New Releases</H1
+><DIV
+CLASS="warning"
+><P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>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.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
><P
>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