summaryrefslogtreecommitdiff
path: root/Porting/release_managers_guide.pod
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2011-06-10 13:27:21 -0700
committerFather Chrysostomos <sprout@cpan.org>2011-06-10 13:27:45 -0700
commit21768cb3b7803f58d5e8a4d116f01abe3014272c (patch)
tree052ae03f7bd874e59bce1abd479a379b9577b13e /Porting/release_managers_guide.pod
parenta15bfc9e2304470503968445191dc51fa75f3b82 (diff)
downloadperl-21768cb3b7803f58d5e8a4d116f01abe3014272c.tar.gz
Correct example commit in release_managers_guide.pod; add example
The 8891dd8d commit mentioned in the perlNNNdelta section is actually an example of a perl version bump. So I’ve copied it to that section and replaced the commit id in the perlNNNdelta section with dd885b5, which *is* a perlNNNdelta TOC update.
Diffstat (limited to 'Porting/release_managers_guide.pod')
-rw-r--r--Porting/release_managers_guide.pod8
1 files changed, 6 insertions, 2 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index e6ca378219..35e136b190 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -308,6 +308,10 @@ Commit your changes:
$ git commit -a -m 'Bump the perl version in various places for 5.x.y'
+At this point you may want to compare the commit with a previous bump to
+see if they look similar. See commit 8891dd8d for an example of a
+previous version bump.
+
When the version number is bumped, you should also update Module::CoreList
(as described below in L<"update Module::CoreList">) to reflect the new
version number.
@@ -962,8 +966,8 @@ Finally, commit:
$ git commit -a -m 'update TOC for perlNNNdelta'
-At this point you may want to compare the commit with a previous bump to
-see if they look similar. See commit 8891dd8d for an example of a
+At this point you may want to compare the commit with a previous bump to
+see if they look similar. See commit dd885b5 for an example of a
previous version bump.