summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJesse Vincent <jesse@bestpractical.com>2010-03-29 09:47:10 -0400
committerJesse Vincent <jesse@bestpractical.com>2010-03-29 09:47:10 -0400
commit66d8ce14f1c15a760d12951a45f0791a7734cea5 (patch)
tree4abc8f117f04c2622d25bfba783ff48427b89bf4
parent233ca920f2b8dfe79c3bdcfadc6ba9e459d98838 (diff)
downloadperl-66d8ce14f1c15a760d12951a45f0791a7734cea5.tar.gz
back out misguided change to brnaching time.
-rw-r--r--Porting/release_managers_guide.pod10
1 files changed, 5 insertions, 5 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 19a6884dbe..f104b47a1c 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -945,12 +945,12 @@ all the C<d> (deferred) flags to C<.> (needs review).
=item *
-I<You MUST SKIP this step for BLEAD>
+I<You MUST SKIP this step for RC, BLEAD>
-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.
+If this was the first release of a new maint series, (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> ]