In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/d60a10440915acb0ef0fef797a3146b6b7423c83?hp=4cc80fc4cbbd82e20f7b14b68abb53d552076022>
- Log ----------------------------------------------------------------- commit d60a10440915acb0ef0fef797a3146b6b7423c83 Author: David Mitchell <[email protected]> Date: Fri Aug 14 00:29:30 2009 +0100 release_managers_guide: add release compare item, and expand a couple of sections. ----------------------------------------------------------------------- Summary of changes: Porting/release_managers_guide.pod | 32 ++++++++++++++++++++++++++------ 1 files changed, 26 insertions(+), 6 deletions(-) diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 1102ca7..e7b5c63 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -2,11 +2,10 @@ release_managers_guide - Releasing a new version of perl 5.x -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 +As of August 2009, this fule is mostly complete, although it is missing +some detail on doing a mjor release (e.g. 5.10.0 -> 5.12.0). Note that +things change at each release, so there may be new things not covered +here, or tools may need updating. =head1 SYNOPSIS @@ -68,7 +67,13 @@ the tarball will usually be the same as that of the previous release. =item Release Candidate (RC) -XXX Describe me +A release candidate is an attempt to produce a tarball that is a close as +possible to the final release. Indeed, unless critical faults are found +during the RC testing, the final release will be identical to the RC +barring a few minor fixups (updating the release date in F<perlhist.pod>, +removing the RC status from F<patchlevel.h>, etc). If faults are found, +then the fixes should be put into a new release candidate, never directly +into a final release. =item Stable/Maint release @@ -624,6 +629,21 @@ which is why you should test from the tarball. =item * +Compare the pathnames of all installed files with those of the previous +release (i.e. against the last installed tarball on this branch which you +have previously verified using this same procedure). In particular, look +for files in the wrong place, or files no longer included which should be. +For example, suppose the about-to-be-released version is 5.10.1 and the +previous is 5.10.0: + + cd installdir-5.10.0/ + find . -type f | perl -pe's/5\.10\.0/5.10.1/g' | sort > /tmp/f1 + cd installdir-5.10.1/ + find . -type f | sort > /tmp/f2 + diff -u /tmp/f[12] + +=item * + Bootstrap the CPAN client on the clean install: $ ./bin/perl -MCPAN -e'shell' -- Perl5 Master Repository
