From: Michael Smith Date: Fri, 28 Dec 2007 04:49:48 +0000 (+0000) Subject: Clarify which parts of the release-notes source file need to be X-Git-Tag: release/1.79.1~6^2~1570 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=51fa0f45c0bb2a1e1d6e1403f6f9ab0f41269d7a;p=docbook-dsssl Clarify which parts of the release-notes source file need to be added/edited for each release. --- diff --git a/xsl/README.BUILD b/xsl/README.BUILD index bfaf3ab40..9274eaf9d 100644 --- a/xsl/README.BUILD +++ b/xsl/README.BUILD @@ -341,21 +341,23 @@ safely ignore this part. 4. Open the NEWS.xml file in your text/XML editor, select the sect1 section and all its child content, and paste that into - the RELEASE-NOTES.xml file, as the first sect1 child of the - RELEASE-NOTES.xml file's root article element. - -5. In the RELEASE-NOTES.xml file, add a variablelist with a - varlistentry instance for each major significant change made in - this release that merits special mention in the release notes; - generally, that means every major enhancement. - -6. In the RELEASE-NOTES.xml, in the content you have just pasted - in, go through each sect2 section and manually remove any - listitem instances that have content which doesn't need to be - included in the final release notes. In general, that means - removing most bug fixes and "housekeeping" changes that do not - need to be exposed to users, but changes for feature - enhancements or changes to public APIs. + the RELEASE-NOTES.xml file, as the second sect1 child of the + RELEASE-NOTES.xml file's root article element (just after the + section). + +5. In the section you just pasted from the NEWS.xml file into the + RELEASE-NOTES.xml file, add a variablelist with a varlistentry + instance for each major significant change made in this release + that merits special mention in the release notes; generally, + that means every major enhancement. + +6. In the section you just pasted from the NEWS.xml file into the + RELEASE-NOTES.xml file, go through each sect2 section and + manually remove any listitem instances that have content which + doesn't need to be included in the final release notes. In + general, that means removing most bug fixes and "housekeeping" + changes that do not need to be exposed to users, but changes + for feature enhancements or changes to public APIs. 7. After making all changes/additions to the RELEASE-NOTES.xml file, check it back in with