summaryrefslogtreecommitdiff
path: root/Porting/release_managers_guide.pod
diff options
context:
space:
mode:
authorJesse Vincent <jesse@bestpractical.com>2009-07-29 18:03:35 -0400
committerDavid Mitchell <davem@iabyn.com>2009-08-03 22:06:00 +0100
commit22f9d23c00832ca9e5603fbd620b5fc888d17468 (patch)
treedd8cdb2340ba65c9327d7a59db4d20bc8c19a205 /Porting/release_managers_guide.pod
parent310092307d67eb0216a59567cd5d4c302a9eed80 (diff)
downloadperl-22f9d23c00832ca9e5603fbd620b5fc888d17468.tar.gz
add 'regen' steps to the release_managers_guide
(cherry picked from commit 55878aed38c1e1d1b71b3f10e7f6620fcc0158e8)
Diffstat (limited to 'Porting/release_managers_guide.pod')
-rw-r--r--Porting/release_managers_guide.pod16
1 files changed, 16 insertions, 0 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 2896716b07..b8324a1436 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -285,6 +285,22 @@ 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.
+=item *
+
+Check that files managed by F<regen.pl> and friends are up to date. From
+within your working directory:
+
+
+ $ git st
+ $ make regen
+ $ make regen_perly
+ $ git st
+
+If any of the files managed by regen.pl have changed, then you should commit
+the updated versions:
+
+ $ git commit -m 'Updated files generated by regen tools for perl 5.x.y' <list of files>
+
=item *