release-notes/devel README.fedora-release,1.4,1.5

[Paul W. Frields (pfrields)]

Author: pfrields

Update of /cvs/docs/release-notes/devel
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24231

Modified Files:
	README.fedora-release 
Log Message:
Update notes for f13


Index: README.fedora-release
===================================================================
RCS file: /cvs/docs/release-notes/devel/README.fedora-release,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- README.fedora-release	13 Dec 2006 01:19:47 -0000	1.4
+++ README.fedora-release	27 Jan 2007 22:13:57 -0000	1.5
@@ -5,14 +5,23 @@
 If you want to turn the current release notes into a SRPM package for
 import to Core, do the following:
 
-1.  Make sure you have the release-notes/ module, the homepage/
-    module, and the docs-common/ module -- all in Docs CVS -- in the
-    same location.
-
-2.  In the homepage/ module, do "make release-pkg".  This builds a
-    tarball for use in the release-notes SRPM.  Copy the tarball to
-    the release-notes/ folder.  *Make sure the release number of the
-    homepage tarball matches that for the relesae-notes!*
+1.  Make sure you have the following modules at the same tree depth.
+    These are all found in Docs CVS.
+
+    * release-notes/
+    * docs-common/
+
+    SUPPLEMENTALS:
+    * about-fedora/
+    * homepage/
+    * readme/
+    * readme-burning-isos/
+
+2.  In each module in the "SUPPLEMENTAL" list, do "make release-pkg".
+    This builds a tarball for use in the release-notes SRPM.  Copy the
+    tarball to the release-notes/ folder.  *Make sure the release
+    number of the homepage tarball matches that for the
+    release-notes!*
 
 3.  Edit the fedora-release-notes.spec file and edit the "Release" tag
     and make a new entry in the %changelog.  There is no need to use
@@ -24,4 +33,4 @@
     you want to review them.  The tarball is there as well.
 
 
--- PWF, rev. 12 Dec 2006
+-- PWF, rev. 27 Jan 2007