Minor update to docs for parrot release number in build/PARROT_REVISION.

rakudo · Jul 7, 2009 · 4549f3c · 4549f3c
1 parent 19b8db2
commit 4549f3c
Showing 1 changed file with 5 additions and 4 deletions.
diff --git a/docs/release_guide.pod b/docs/release_guide.pod
@@ -80,10 +80,11 @@ prior to the release, addressing them as needed.
 
 Once Parrot issues its monthly release, edit Rakudo's 
 build/PARROT_REVISION file to contain the subversion revision 
-number corresponding to Parrot's monthly release.  
-As always, test to make sure Rakudo still builds and
-passes its tests.  Once build/PARROT_REVISION has been
-set to the Parrot release, it must not be changed until
+number and release number corresponding to Parrot's monthly 
+release.  For example, for June 2009 PARROT_REVISION file
+contained "39599 1.3.0".  As always, test to make sure Rakudo 
+still builds and passes its tests.  Once build/PARROT_REVISION 
+has been set to the Parrot release, it must not be changed until
 after the Rakudo release.  In other words, we want each
 monthly release of Rakudo to be able to be built using
 the immediately prior release of Parrot.