Add Debbugs::BugWalker to abstract out bug-walking code in

[debbugs.git] / UPGRADE

diff --git a/UPGRADE b/UPGRADE
index ff61fd0b995d3540370a048997a80c4e47c94fc3..b4ab626b93ee6d30347a9a6aa24d2bdd03ec3e26 100644 (file)
--- a/UPGRADE
+++ b/UPGRADE
@@ -2,6 +2,36 @@
                             Debbugs upgrade notes
                            +=====================+
 
+From 2.4.1 to 2.4.2
+-------------------
+
+The file format used to store the status of a bug (package, severity, etc.)
+has changed; it is now in an RFC822-like format in order to be more
+extensible, and is written to .summary files rather than the old .status
+files. Before accepting any mail with the new version of debbugs, you must
+run the 'debbugs-upgradestatus' program over your bug spool. The old .status
+files will be left intact, and will continue to be written in sync with the
+.summary files for compatibility with external tools.
+
+There is a new standalone spam-scanning script called spamscan, which uses
+the SpamAssassin modules. To use it, set the $gSpamScan variable in
+/etc/debbugs/config to a true value and $gSpamMailbox to an mbox file to
+which detected spam should be appended, add /usr/lib/debbugs/spamscan to
+your crontab as per the example, and optionally set $gSpamRulesDir and
+$gSpamLocalTestsOnly as desired.
+
+From 2.4 to 2.4.1
+-----------------
+
+Add the following variables to the /etc/debbugs/config file:
+
+$gHTMLSuffix = ".html";
+
+The use of $gCGIDomain has been cleaned up; formerly, it needed to begin
+with "http://", which was confusingly inconsistent with all the other domain
+variables. If you worked around this in your configuration, you will need to
+recheck it.
+
 From 2.3 to 2.4
 ---------------