upgrade instructions

diff --git a/CHANGES b/CHANGES
index 0209e01ef6c9d2352618f1a004930179e6de7f86..cb8df1a06404264d04654558c8c43b02fef50e76 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,6 +1,6 @@
 See ChangeLog.d/* for detailed revision history.
 
-* Changes up to version 1.6
+* Changes up to version 2.0
 
 ** General
 

diff --git a/README.upgrades b/README.upgrades
index 88d0d3b8a4f98c62e2a89721a84f90df3d974120..a79767b0108f9b39a938ede9d2816ab68d4a177d 100644 (file)
--- a/README.upgrades
+++ b/README.upgrades
@@ -4,6 +4,7 @@ The general procedure is:
 
  * stop the old daemon, e.g. with
      /etc/init.d/disorder stop
+ * back up your database
  * build and install the new version as described in the README
  * update the configuration files (see below)
  * start the new daemon, e.g. with
@@ -14,7 +15,26 @@ upgrading between particular versions.  Minor versions are not
 explicitly mentioned; a version number like 1.1 implicitly includes
 all 1.1.x versions.
 
-* 1.5 -> 1.6
+* 1.5 -> 2.0
+
+** Database upgrade
+
+The first thing the server does when upgrading from 1.5 is run the
+disorder-dbupgrade program.  This is necessary to modify any non-ASCII track
+names to meet the latest version's stricter normalization practices.  The
+upgrade should succeed automatically; if not it should leave an error message
+in syslog.
+
+It is strongly recommended that you back up your database before performing the
+upgrade.  For example, as root, with the server STOPPED:
+  cd /var/disorder
+  mkdir BACKUP
+  cp -p * BACKUP
+
+To restore, again as root:
+  cd /var/disorder
+  rm *
+  cp -p BACKUP/* .
 
 ** 'transform' and 'namepart' directives