In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/bc4c40f2eb948644a92225726b3cab20f98488f7?hp=f662f3b795bf72e495d34174bea334bddb3c6d0f>
- Log ----------------------------------------------------------------- commit bc4c40f2eb948644a92225726b3cab20f98488f7 Author: Jesse Vincent <[email protected]> Date: Fri Oct 9 00:13:06 2009 -0400 Slightly clean up the release manager guide by specifying an "End here for SNAPSHOT" per DAPM M Porting/release_managers_guide.pod commit ee76d676860a90e36e25796e40b756319ee50779 Author: Jesse Vincent <[email protected]> Date: Fri Oct 9 00:03:37 2009 -0400 Document that blead is released by a member of the sucker-of-the-month club. M Porting/release_managers_guide.pod ----------------------------------------------------------------------- Summary of changes: Porting/release_managers_guide.pod | 41 +++++++++++++---------------------- 1 files changed, 15 insertions(+), 26 deletions(-) diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index bbdfdf5..daa4fcc 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -14,7 +14,9 @@ manual - to produce a perl release of some description, be that a snaphot, release candidate, or final, numbered release of maint or blead. The release process has traditionally been executed by the current -pumpking. +pumpking. Blead releases from 5.11.0 forward are made each month on the +20th by a non-pumpking release engineer. The release engineer roster +and schedule can be found in Porting/release_schedule.pod. This document both helps as a check-list for the release engineer and is a base for ideas on how the various tasks could be automated @@ -717,7 +719,9 @@ Install an XS module, for example: =item * -I<You MAY SKIP this step for SNAPSHOT> +I<If you're building a SNAPSHOT, you should STOP HERE> + +=item * Check that the C<perlbug> utility works. Try the following: @@ -741,8 +745,6 @@ report. Check that it shows up, then remember to close it! =item * -I<You MAY SKIP this step for SNAPSHOT> - Wait for the smoke tests to catch up with the commit which this release is based on (or at least the last commit of any consequence). @@ -752,8 +754,6 @@ back and fix things. =item * -I<You MUST SKIP this step for SNAPSHOT> - Once smoking is okay, upload it to PAUSE. This is the point of no return. If anything goes wrong after this point, you will need to re-prepare a new release with a new minor version or RC number. @@ -766,9 +766,6 @@ Upload both the .gz and .bz2 versions of the tarball. =item * -I<You MUST SKIP this step for SNAPSHOT> - - Now that you've shipped the new perl release to PAUSE, it's time to publish the tag you created earlier to the public git repo: @@ -776,8 +773,6 @@ time to publish the tag you created earlier to the public git repo: =item * -I<You MUST SKIP this step for SNAPSHOT> - Disarm the F<patchlevel.h> change; for example, static const char * const local_patches[] = { @@ -797,21 +792,17 @@ Mail p5p to announce your new release, with a quote you prepared earlier. =item * -I<You MAY SKIP this step for SNAPSHOT> - Wait 24 hours or so, then post the announcement to use.perl.org. (if you don't have access rights to post news, ask someone like Rafael to do it for you.) =item * -I<You MUST SKIP this step for SNAPSHOT> - Ask Jarkko to add the tarball to http://www.cpan.org/src/ =item * -I<You MUST SKIP this step for SNAPSHOT, RC, BLEAD> +I<You MUST SKIP this step for RC, BLEAD> Ask Jarkko to update the descriptions of which tarballs are current in http://www.cpan.org/src/README.html, and Rafael to update @@ -819,14 +810,14 @@ http://dev.perl.org/perl5/ =item * -I<You MUST SKIP this step for SNAPSHOT, RC> +I<You MUST SKIP this step for RC> Remind the current maintainer of C<Module::CoreList> to push a new release to CPAN. =item * -I<You MUST SKIP this step for SNAPSHOT, RC> +I<You MUST SKIP this step for RC> Bump the perlXYZ version number. @@ -888,14 +879,14 @@ previous version bump. =item * -I<You MUST SKIP this step for SNAPSHOT, RC, BLEAD> +I<You MUST SKIP this step for RC, BLEAD> If this was a maint release, then edit F<Porting/mergelog> to change all the C<d> (deferred) flags to C<.> (needs review). =item * -I<You MUST SKIP this step for SNAPSHOT, RC, BLEAD> +I<You MUST SKIP this step for RC, BLEAD> If this was a major release (5.x.0), then create a new maint branch based on the commit tagged as the current release and bump the version @@ -908,7 +899,7 @@ XXX need a git recipe =item * -I<You MUST SKIP this step for SNAPSHOT, RC, BLEAD> +I<You MUST SKIP this step for RC, BLEAD> Copy the perlNNNdelta.pod for this release into the other branches; for example: @@ -919,7 +910,7 @@ example: Edit F<pod.lst> to add an entry for the file, e.g.: perl5101delta Perl changes in version 5.10.1 - + Then rebuild various files: $ perl pod/buildtoc --build-all @@ -930,8 +921,6 @@ Finally, commit: =item * -I<You MUST SKIP this step for SNAPSHOT> - Make sure any recent F<pod/perlhist.pod> entries are copied to F<perlhist.pod> on other branches; typically the RC* and final entries, e.g. @@ -942,8 +931,8 @@ e.g. =item * -I<You MUST RETIRE to your preferred PUB, CAFE or SEASIDE VILLA for some much-needed -rest and relaxation>. +I<You MUST RETIRE to your preferred PUB, CAFE or SEASIDE VILLA for some +much-needed rest and relaxation>. Thanks for releasing perl! -- Perl5 Master Repository
