Author: particle Date: Tue Mar 13 06:47:09 2007 New Revision: 17460 Modified: trunk/docs/project/release_manager_guide.pod
Log: [docs]: update release instructions ~ add note about removing DEVELOPING and it's manifest entry ~ provide links to some related documents Modified: trunk/docs/project/release_manager_guide.pod ============================================================================== --- trunk/docs/project/release_manager_guide.pod (original) +++ trunk/docs/project/release_manager_guide.pod Tue Mar 13 06:47:09 2007 @@ -49,8 +49,7 @@ =item d -Update F<ChangeLog>, F<NEWS>, F<docs/parrothist.pod>, F<docs/ROADMAP.pod>, -and F<docs/BROKEN.pod>. +Update F<ChangeLog>, F<NEWS>, F<docs/parrothist.pod>, and F<docs/ROADMAP.pod>. =item e @@ -87,6 +86,17 @@ =item 4. +Prepare the release tarball. + +=over 4 + +=item a + +Delete F<DEVELOPING>, and it's corresponding F<MANIFEST> entry. +This file should never appear in a release. + +=item b + Make the release tarball: $ make release VERSION=a.b.c @@ -94,6 +104,8 @@ where a.b.c is the version number. This will create the tarball named F<parrot-a.b.c.tar.gz>. +=back + =item 5. Untar F<parrot-a.b.c.tar.gz> into another area. @@ -171,6 +183,10 @@ once where the F<MANIFEST> check failed. The intent of this file is to document what must be done to release so that such mistakes don't happen again. +=head1 SEE ALSO + +F<README>, F<RESPONSIBLE_PARTIES>. + =head1 Appendix 1 parrot repository layout as of end of Apr 2005
