In perl.git, the branch maint-5.10 has been updated <http://perl5.git.perl.org/perl.git/commitdiff/7f14495b6817f771912517c46a51ce0e28d09b8a?hp=81a6d87b05711a71bcbe0d2a4893901613af1733>
- Log ----------------------------------------------------------------- commit 7f14495b6817f771912517c46a51ce0e28d09b8a Author: David Mitchell <[email protected]> Date: Sat Jul 25 00:21:25 2009 +0100 tweaks to release_managers_guide.pod (cherry picked from commit 636a19183afddcfee3e377f79668687caee21a8f) M Porting/release_managers_guide.pod commit a4cc53ea319ad306d44bef015cfde3d2dfb2a60d Author: David Mitchell <[email protected]> Date: Fri Jul 24 23:42:39 2009 +0100 mention Deprecations in how_to_write_a_perldelta.pod (cherry picked from commit 87b6d2691f69f385919a2dd70800297d8f5cd295) M Porting/how_to_write_a_perldelta.pod commit 16d736372d7bfa0705276a9c27195b79342a7ae3 Author: David Mitchell <[email protected]> Date: Fri Jul 24 15:57:32 2009 +0100 bump-perl-version missed "perl5.10.0" style strings ("perl-5.10.0" was matched, but without the "-", it failed) (cherry picked from commit 8b8cdb3af135a75c41bb19ee20a85445163f4cff) M Porting/bump-perl-version commit 68d546c9ab63ec86d3f4cf76c996090bd96b4732 Author: David Mitchell <[email protected]> Date: Fri Jul 24 15:55:27 2009 +0100 minor tweaks to release_managers_guide.pod (cherry picked from commit dc0a62a1fb49c5436d458316262c2453e0848f7f) M Porting/release_managers_guide.pod ----------------------------------------------------------------------- Summary of changes: Porting/bump-perl-version | 5 ++- Porting/how_to_write_a_perldelta.pod | 4 +++ Porting/release_managers_guide.pod | 49 +++++++++++++++++++++++++++++---- 3 files changed, 50 insertions(+), 8 deletions(-) diff --git a/Porting/bump-perl-version b/Porting/bump-perl-version index 4d4df83..c84d18d 100755 --- a/Porting/bump-perl-version +++ b/Porting/bump-perl-version @@ -162,14 +162,14 @@ my @maps = ( ], # 5.8.9 [ - qr{\b $oldx\.$oldy\.$oldz \b}x, + qr{ $oldx\.$oldy\.$oldz \b}x, sub {"", "$newx.$newy.$newz"}, undef, ], # 5.008009 [ - qr{\b $old_decimal \b}x, + qr{ $old_decimal \b}x, sub {"", sprintf "%d.%03d%03d", $newx, $newy, $newz }, undef, ], @@ -183,6 +183,7 @@ my %SKIP_FILES = map { ($_ => 1) } qw( Changes MANIFEST Porting/how_to_write_a_perldelta.pod + Porting/bump-perl-version Porting/mergelog Porting/mergelog-tool pod.lst diff --git a/Porting/how_to_write_a_perldelta.pod b/Porting/how_to_write_a_perldelta.pod index 115c689..dd8dac1 100644 --- a/Porting/how_to_write_a_perldelta.pod +++ b/Porting/how_to_write_a_perldelta.pod @@ -174,6 +174,10 @@ Descriptions of platform agnostic bugs we know we can't fix go here. Any tests that had to be C<TODO>ed for the release would be noted here, unless they were specific to a particular platform (see below). +=item Deprecations + +Add any new known deprecations here. + =item Platform Specific Notes Any changes specific to a particular platform. VMS and Win32 are the usual diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index f418197..daf62e0 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -3,7 +3,11 @@ release_managers_guide - Releasing a new version of perl 5.x -XXX as of Jul 2009, this file is still a work-in-progress - DAPM +XXX as of Jul 2009, this file is still a work-in-progress. I think it +contains all the actions needed to build a release, but things may have +got skipped, and some things could do with polishing. Note that things +change each release, there may be new things not covered here, or +tools may need updating. DAPM =head1 SYNOPSIS @@ -17,9 +21,9 @@ This document both helps as a check-list for the pumpking and is a base for ideas on how the various tasks could be automated or distributed. -The outline of a release cycle is as follows: +The outline of a typical release cycle is as follows: - (5.10.1 is released, and post-release action have been done) + (5.10.1 is released, and post-release actions have been done) ...time passes... @@ -30,6 +34,8 @@ The outline of a release cycle is as follows: a few weeks before the release, a number of steps are performed, including bumping the version to 5.10.2 + + ...a few weeks passes... perl-5.10.2-RC1 is released @@ -188,6 +194,12 @@ To see which core distro versions differ from the current CPAN versions: ./perl -Ilib Porting/core-cpan-diff -x -a +if you are making a maint release, run C<core-cpan-diff> on both blead and +maint, then diff the two outputs. Compare this with what you expect, and if +necessary, fix things up. For example, you might think that both blead +and maint are synchronised with a particular CPAN module, but one might +have some extra changes. + =item * Ensure dual-life CPAN modules are stable, which comes down to: @@ -216,6 +228,11 @@ Similarly, monitor the smoking of core tests, and try to fix. =item * +Similarly, monitor the smoking of perl for compiler warnings, and try to +fix. + +=item * + Run F<Porting/cmpVERSION.pl> to compare the current source tree with the previous version to check for for modules that have identical version numbers but different contents, e.g.: @@ -241,7 +258,9 @@ also sensible. =item * Get perldelta in a mostly finished state. -XXX expand +Peruse F<Porting/how_to_write_a_perldelta.pod>, and try to make sure that +every section it lists is, if necessary, populated and complete. Copy +edit the whole document. =item * @@ -279,6 +298,12 @@ README.vms needs special handling: rename perl-5^.10^.1.dir perl-5_10_1.dir + +=item * + +Review and update INSTALL to account for the change in version number; +in particular, the "Coexistence with earlier versions of perl 5" section. + =item * Update the F<Changes> file to contain the git log command which would show @@ -293,6 +318,7 @@ correct incantation: replace the not-yet-created tag with C<HEAD> and see if git log produces roughly the right number of commits across roughly the right time period. + =item * Check some more build configurations, e.g. @@ -329,7 +355,9 @@ with git and a lack of Changes files. =head2 Building a release candidate (At this point you should already have performed the actions described in -L</"Actions prior to the first release candidate">.) +L</"Actions prior to the first release candidate">.) You should review +that section to ensure that everything there has done, and to see whether +any of those actions (such as consistency checks) need to be repeated. =over 4 @@ -337,7 +365,10 @@ L</"Actions prior to the first release candidate">.) Re-read the perldelta to try to find any embarrassing typos and thinkos; remove any C<TODO> or C<XXX> flags; and run through pod and spell -checkers. [XXX show how] +checkers, e.g. + + podchecker -warnings -warnings pod/perl5101delta.pod + spell pod/perl5101delta.pod =item * @@ -502,6 +533,12 @@ on the previous filename to look for suitable candidates. =item * +If this was a maintenance release, then edit F<Porting/mergelog> to change +all the C<d> (deferred) flags to C<.> (needs review). + + +=item * + If this was a major release, then =over -- Perl5 Master Repository
