summaryrefslogtreecommitdiff
path: root/Porting/release_managers_guide.pod
diff options
context:
space:
mode:
authorJesse Vincent <jesse@bestpractical.com>2009-10-20 10:54:38 -0400
committerJesse Vincent <jesse@bestpractical.com>2009-10-20 10:54:38 -0400
commit54356a6f6c5b66c92d16521d060160496e44de3c (patch)
tree46dccf9de9bc8d9704716104e18ee7138bd04b14 /Porting/release_managers_guide.pod
parent172dd9593c69d24c1273d593b8e9ca4fadf1f99c (diff)
downloadperl-54356a6f6c5b66c92d16521d060160496e44de3c.tar.gz
release manager guide notes updated
Diffstat (limited to 'Porting/release_managers_guide.pod')
-rw-r--r--Porting/release_managers_guide.pod15
1 files changed, 14 insertions, 1 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index daa4fccb84..8c1c51e6ed 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -241,6 +241,8 @@ Once all version numbers have been bumped, re-run the checks.
Then run again without the -x option, to check that dual-life modules are
also sensible.
+ $ ./perl -Ilib Porting/cmpVERSION.pl -d ~/my_perl-tarballs/perl-5.10.0 .
+
=item *
I<You MAY SKIP this step for SNAPSHOT>
@@ -285,7 +287,7 @@ careful not change text like "this was fixed in 5.10.0"! Then run:
$ Porting/bump-perl-version -u < /tmp/scan
-which will update all the files shown; then commit the changes.
+which will update all the files shown.
Be particularly careful with F<INSTALL>, which contains a mixture of
C<5.10.0>-type strings, some of which need bumping on every release, and
@@ -295,6 +297,17 @@ this line in README.vms needs special handling:
rename perl-5^.10^.1.dir perl-5_10_1.dir
+Have a look a couple lines up from that. You'll see roman numerals.
+Update those too. Find someone with VMS clue if you have to update
+the Roman numerals for a .0 release.
+
+Commit your changes:
+
+ $ git st
+ $ git diff
+ B<review the delta carefully>
+
+ $ git commit -a -m 'Bump the perl version in various places for 5.x.y'
=item *