Begin bowing to public pressure toward an open blead;

document how to create a maint branch when RC1 comes out.

diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index ffd02a4..19a6884 100644 (file)
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -945,16 +945,20 @@ all the C<d> (deferred) flags to C<.> (needs review).
 
 =item *
 
-I<You MUST SKIP this step for RC, BLEAD>
+I<You MUST SKIP this step for BLEAD>
 
-If this was a major release (5.x.0), then create a new maint branch 
-based on the commit tagged as the current release and bump the version 
-in the blead branch in git, e.g. 5.12.0 to 5.13.0.
+If this was the first release candidate for a major release of maint
+(5.x.0 where x is even), then create a new maint branch based on the
+commit tagged as the current release and bump the version in the blead
+branch in git, e.g. 5.12.0 to 5.13.0.
 
 [ XXX probably lots more stuff to do, including perldelta,
 C<lib/feature.pm> ]
 
-XXX need a git recipe
+Assuming you're using git 1.7.x or newer:
+
+    $ git checkout -b maint-5.12
+    $ git push origin -u maint-5.12
 
 =item *