In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/55878aed38c1e1d1b71b3f10e7f6620fcc0158e8?hp=3d967d9abef744c6fe8f4b6b7434a38c59380228>
- Log ----------------------------------------------------------------- commit 55878aed38c1e1d1b71b3f10e7f6620fcc0158e8 Author: Jesse Vincent <[email protected]> Date: Wed Jul 29 18:03:35 2009 -0400 add 'regen' steps to the release_managers_guide ----------------------------------------------------------------------- Summary of changes: Porting/release_managers_guide.pod | 16 ++++++++++++++++ 1 files changed, 16 insertions(+), 0 deletions(-) diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 2896716..b8324a1 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 * -- Perl5 Master Repository
