Some updates to the documentation of the increasingly broken build process

diff --git a/xsl/README.BUILD b/xsl/README.BUILD
index bec0401f4a88136fce240e2bcc97d93796008613..ade1bdd63c7eb8c2e0ad72a305d797f8694ef0a9 100644 (file)
--- a/xsl/README.BUILD
+++ b/xsl/README.BUILD
@@ -602,13 +602,17 @@ SourceForge, see
 -----------------------------------------------------------------
 Part 6: Manage release files
 -----------------------------------------------------------------
-This section explains how to manage release files using the
-file-management interface at Sourceforge.
+
 
 Unfortunately, Sourceforge provides no automated way to manage
 file releases, so you must complete all the following steps using
 the SF file-management Web interface.
 
+The file-management Web interface has been updated. Please ee:
+https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download
+
+Here are the legacy instructions for reference *only*:
+
 NOTE: Try hard to make sure you've got everything prepared OK,
 because the SF file-management system is extremely unwieldy, and
 it makes unwinding an upload mistake a major PITA. If you do make
@@ -795,6 +799,32 @@ This section explains how to announce a release.
 
         http://sourceforge.net/news/?group_id=21935
 
+-----------------------------------------------------------------
+Part 11: Do post-release wrap-up
+-----------------------------------------------------------------
+This section explains the "wrap up" steps you need to do
+following an official release.
+
+1. Open the VERSION file.
+
+2. Change the content of the PreviousRelease element to the
+   version number you have just released.
+
+3. Change the content of the PreviousReleaseRevision element to
+   the number of the repository revision from which you built the
+   release.
+
+4. Change the content of the fm:Version element to the version
+   number of the next anticipated release, with the string "-pre"
+   appended; for example:
+
+     <fm:Version>1.73.1-pre</fm:Version>
+
+9. Check the VERSION file back in.
+
+    svn commit \
+      -m "Restored VERSION file to snapshot state" VERSION
+
 -----------------------------------------------------------------
 Part 9: Prepare for Freshmeat update
 -----------------------------------------------------------------
@@ -861,31 +891,6 @@ following steps.
 
      make freshmeat-ns SFRELID=NNNNNN FMGO=
 
------------------------------------------------------------------
-Part 11: Do post-release wrap-up
------------------------------------------------------------------
-This section explains the "wrap up" steps you need to do
-following an official release.
-
-1. Open the VERSION file.
-
-2. Change the content of the PreviousRelease element to the
-   version number you have just released.
-
-3. Change the content of the PreviousReleaseRevision element to
-   the number of the repository revision from which you built the
-   release.
-
-4. Change the content of the fm:Version element to the version
-   number of the next anticipated release, with the string "-pre"
-   appended; for example:
-
-     <fm:Version>1.73.1-pre</fm:Version>
-
-9. Check the VERSION file back in.
-
-    svn commit \
-      -m "Restored VERSION file to snapshot state" VERSION
 
 -----------------------------------------------------------------
 NOTES

diff --git a/xsl/RELEASE-NOTES.xml b/xsl/RELEASE-NOTES.xml
index bfc418cff1eee4d7de7cace693e23251c6a40192..3c9aef0df5d7def4d270ad7576287fa0e1256476 100644 (file)
--- a/xsl/RELEASE-NOTES.xml
+++ b/xsl/RELEASE-NOTES.xml
@@ -62,6 +62,12 @@ public APIs (user-configurable parameters).</para>
 <para>This release includes important bug fixes and adds the following
 significant feature changes:</para>
 <variablelist>
+<varlistentry>
+<term>Webhelp</term>
+<listitem><para>A new browser-based, cross-platform help format with full-text search and other features typically found in help systems. See <filename>webhelp/docs/content/ch01.html</filename> for more information and a demo. </para></listitem>
+
+</varlistentry>
+
 <varlistentry>
 <term>Gentext</term>
 <listitem><para>Many updates and additions to translation/locales thanks to Red Hat, the Fedora Project, and other contributors.</para></listitem>