release-notes/devel README.fedora-release,1.1,1.2
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Tue Aug 1 23:54:30 UTC 2006
Author: pfrields
Update of /cvs/docs/release-notes/devel
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6829
Modified Files:
README.fedora-release
Log Message:
Update the README for use by Core packagers
Index: README.fedora-release
===================================================================
RCS file: /cvs/docs/release-notes/devel/README.fedora-release,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README.fedora-release 18 Jul 2006 23:47:09 -0000 1.1
+++ README.fedora-release 1 Aug 2006 23:54:28 -0000 1.2
@@ -5,13 +5,16 @@
If you want to turn the current release notes into a SRPM package for
import to Core, do the following:
-1. Edit the fedora-release-notes.spec file and edit the "Release" tag
-and make a new entry in the %changelog. *DO NOT FORGET* to put %{?dist}
-at the end of the EVR (Epoch/Version/Release) on your %changelog entry's
-first line. (We don't define %dist in Docs CVS, but it *is* in the
-specfile, so the Core system should use it.)
+1. Make sure you have the release-notes/ module and the docs-common/
+module -- also in Docs CVS -- in the same location.
-2. Run 'make release-srpm' to build the SRPM. The contents of the
+2. Edit the fedora-release-notes.spec file and edit the "Release" tag
+and make a new entry in the %changelog. *DO NOT FORGET* to put
+%{?dist} at the end of the EVR (Epoch/Version/Release) on your
+%changelog entry's first line. (We don't define %dist in Docs CVS,
+but it *is* in the specfile, so the Core system should use it.)
+
+3. Run 'make release-srpm' to build the SRPM. The contents of the
source tarball -- the ones not already in the top-level directory --
remain in the "fedora-release-notes-<version>/" directory if you want to
review them. The tarball is there as well.
More information about the Fedora-docs-commits
mailing list