From: Rafael Garcia-Suarez <rgarciasuarez@gmail.com>
Date: Tue, 11 Dec 2007 17:01:05 +0000 (+0000)
Subject: Some things a pumpking should not forget when releasing a new perl
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=15839b602c28a4faab40f7355ab0fef473169850;p=p5sagit%2Fp5-mst-13.2.git

Some things a pumpking should not forget when releasing a new perl

p4raw-id: //depot/perl@32609
---

diff --git a/Porting/pumpkin.pod b/Porting/pumpkin.pod
index 3e13cdd..f0f5800 100644
--- a/Porting/pumpkin.pod
+++ b/Porting/pumpkin.pod
@@ -584,6 +584,15 @@ detailed descriptions ought to be easily available somewhere.
 If you update the subversion number in F<patchlevel.h>, you may need
 to change the version number near the top of the F<Changes> file.
 
+=head2 Bumping perl's version
+
+If you bump perl's version, you will need to update a few things:
+the L<perlhist> manpage for the date of release, the version number and
+perldelta reference in the top level F<README> (and maybe the copyright
+year too), the F<META.yml> file (generated via F<Porting/makemeta>, be
+sure to run it with the current bleadperl), and the meta-info about
+dual-lived modules in Module::Corelist (F<Porting/corelist.pl> does that).
+
 =head2 Todo
 
 The F<pod/perltodo.pod> file contains a roughly-categorized unordered