In perl.git, the branch maint-5.10 has been updated <http://perl5.git.perl.org/perl.git/commitdiff/5348debf9fd57fc15c26529386769684fab96e57?hp=1a2b1ec40398651b4eec31051f44ecc2e0738f9c>
- Log ----------------------------------------------------------------- commit 5348debf9fd57fc15c26529386769684fab96e57 Author: David Mitchell <[email protected]> Date: Sat Aug 22 23:20:57 2009 +0100 today's merging activity M Porting/mergelog commit 50664cb9a854dde4cec14b11f5f847cb9ba3a449 Author: David Mitchell <[email protected]> Date: Sat Aug 22 23:17:57 2009 +0100 more release_managers_guide tweaks (cherry picked from commit 52a66c2cc3722485e8a16f1da9c026524180ca8c) M Porting/release_managers_guide.pod commit 0ddcc1161b4c1eef4023b1c017e0fa6a9a912d62 Author: David Mitchell <[email protected]> Date: Sat Aug 22 22:57:29 2009 +0100 add new release to perlhist M pod/perlhist.pod commit 09c1b3de15b764c5ff3b2243e48439556892547b Author: David Mitchell <[email protected]> Date: Sat Aug 22 22:51:15 2009 +0100 Update Module::CoreList for 5.10.1 (cherry picked from commit 6c1a81b03e170d09e3d9f2bb12f4ab9cafe03986) M lib/Module/CoreList.pm ----------------------------------------------------------------------- Summary of changes: Porting/mergelog | 34 ++++++++++++ Porting/release_managers_guide.pod | 99 ++++++++++++++++++++---------------- lib/Module/CoreList.pm | 4 +- pod/perlhist.pod | 1 + 4 files changed, 92 insertions(+), 46 deletions(-) diff --git a/Porting/mergelog b/Porting/mergelog index ce23834..3a77b64 100644 --- a/Porting/mergelog +++ b/Porting/mergelog @@ -3921,3 +3921,37 @@ d c5764f7084 2009/08/18 Convert perl version check in import() from run ti d 7064c127dd 2009/08/18 No need to flush the package's MRO cache if we've d f7fd2659b1 2009/08/18 Flush the MRO cache at the end, rather than the st M 7894ad662a 2009/08/18 Correctly detect NDBM_File availability +M a47a8f3cfe 2009/08/18 Updated Module::CoreList for 5.10.1-RC2 +M a14438df21 2009/08/19 release_managers_guide: minor tweaks +M e9d2e818e0 2009/08/19 bleed and 5.10.1 - documentation fix - README.aix +M 6bc0591006 2009/08/19 bump Safe version to 2.18 +d f89a1e08e6 2009/08/19 Add PERL_DISABLE_PMC to the list of -V's compile-t +M e7598a06d7 2009/08/20 Teach perlivp about the new stucture of the IO::Co +d c3acb9e076 2009/08/20 Perl_newHVhv() should copy immortal values as-is, +d 73519bd018 2009/08/20 Optimise S_mro_get_linear_isa_dfs() when dealing w +d d7c0d2821c 2009/08/20 add -DM flag to track smartmatch resolution +d b0413f463e 2009/08/20 Optimise mro_get_linear_isa_c3() when there is a s +d 04e5ac63d9 2009/08/20 Instead of trusting mro::get_linear_isa(), test it +M b3ed409dee 2009/08/20 incremental improvement in ~~ documentation, alrea + (this was actally applied separately to + blead and maint rather than cherry-picked) +d a18d9f20d1 2009/08/21 In mro_get_linear_isa_c3() optimise even if AvARRA +d 81a8de77c9 2009/08/21 Remove a refactoring typo - don't post-increment $ +d a8ae8fee10 2009/08/21 Use the constant _CAN_PCS to optimise out things t +d f747ebd621 2009/08/21 Add clear magic to %^H so that the HE chain is res +d 17eef65c2f 2009/08/21 Fix build warning in mro.c +d 59d8e2ce29 2009/08/21 Eliminate SV leak in mro::_nextcan - hv_store_ent( +d 8e234d892c 2009/08/21 sv_newmortal() is faster than sv_2mortal(newSV(0)) +d 9c1314f0ea 2009/08/21 gv_efullname3() could return NULL, so mro::_nextca +d c1754fcef4 2009/08/22 In Perl_newATTRSUB(), we know the lengths, so can +d ed4a8a9b7d 2009/08/22 In Perl_newATTRSUB(), refactor the calls to gv_fet +d ae5c1e95b5 2009/08/22 In pp_entersub, replace gv_fetchpv() with gv_fetch +M 74d3927541 2009/08/22 add the CGI "default_value for popup_menu()" fix f +d 68a4c8b9f2 2009/08/22 upgrade GCI from 3.43 to 3.45 +d 0e44158ce9 2009/08/22 re-apply boilerplate to CGI test files +M 0de1c906c3 2009/08/22 better document smart match overloading +M 459fc3ca45 2009/08/22 mention perlivp in release_managers_guide +d 828dad175c 2009/08/22 Eliminate the remaining definitions for *_allocate +d c8e503bfe4 2009/08/22 Eliminate *_ALLOCATED_HEAD and *_HEAD macros which +M 6c1a81b03e 2009/08/22 Update Module::CoreList for 5.10.1 +M 52a66c2cc3 2009/08/22 more release_managers_guide tweaks diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 1855d1a..4b33165 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -148,8 +148,8 @@ in having one for a snapshot, but it's not required). The work of building a release candidate for a numbered release of perl generally starts several weeks before the first release candidate. -Some of these should be done regularly, but all I<must> be done in the -runup to a release. +Some of the following steps should be done regularly, but all I<must> be +done in the run up to a release. =over 4 @@ -171,7 +171,7 @@ 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 +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 @@ -262,11 +262,12 @@ to bump the version further. There is a tool to semi-automate this process. It works in two stages. First, it generates a list of suggested changes, which you review and edit; then you feed this list back and it applies the edits. So, first -scan the source dir looking for likely candidates: +scan the source directory looking for likely candidates. The command line +arguments are the old and new version numbers, and -s means scan: $ Porting/bump-perl-version -s 5.10.0 5.10.1 > /tmp/scan -This produces a file containing a list of suggested edits, eg: +This produces a file containing a list of suggested edits, e.g.: NetWare/Makefile @@ -275,9 +276,10 @@ This produces a file containing a list of suggested edits, eg: i.e. in the file F<NetWare/Makefile>, line 89 would be changed as shown. Review the file carefully, and delete any -/+ line pairs that you don't -want changing. Remember that this tool is largely just grepping for '5.10.0' -or whatever, so it will generate false positives. Be careful not change -text like "this was fixed in 5.10.0"! Then run: +want changing. You can also edit just the C<+> line to change the +suggested replacement text. Remember that this tool is largely just +grepping for '5.10.0' or whatever, so it will generate false positives. Be +careful not change text like "this was fixed in 5.10.0"! Then run: $ Porting/bump-perl-version -u < /tmp/scan @@ -285,9 +287,9 @@ which will update all the files shown; then commit the changes. Be particularly careful with F<INSTALL>, which contains a mixture of C<5.10.0>-type strings, some of which need bumping on every release, and -some of which need to be left. Also note that this tool currently only -performs a single change per line, so in particular, this line in -README.vms needs special handling: +some of which need to be left unchanged. Also note that this tool +currently only detects a single substitution per line: so in particular, +this line in README.vms needs special handling: rename perl-5^.10^.1.dir perl-5_10_1.dir @@ -312,20 +314,27 @@ not-yet created tag for the forthcoming release; e.g. Due to warts in the perforce-to-git migration, some branches require extra exclusions to avoid other branches being pulled in. Make sure you have the 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. - +if C<git log> produces roughly the right number of commits across roughly the +right time period (you may find C<git log --pretty=oneline | wc> useful). =item * -Check some more build configurations, e.g. +Check some more build configurations. The check that setuid builds and +installs is for < 5.11.0 only. + + $ sh Configure -Dprefix=/tmp/perl-5.x.y -Uinstallusrbinperl \ + -Duseshrplib -Dd_dosuid + $ make + $ LD_LIBRARY_PATH=`pwd` make test # or similar for useshrplib - -Duseshrplib -Dd_dosuid - make suidperl + $ make suidperl + $ su -c 'make install' + $ ls -l .../bin/sperl + -rws--x--x 1 root root 69974 2009-08-22 21:55 .../bin/sperl -Check that setuid installs works (for < 5.11.0 only). -XXX any other configs? +(Then delete the installation directory.) +XXX think of other configurations that need testing. =item * @@ -337,14 +346,6 @@ already in F<AUTHORS> $ git log | perl Porting/checkAUTHORS.pl --acknowledged AUTHORS - -=item * - -I<You MAY SKIP this step for SNAPSHOT> - -As there are no regular smokes [ XXX yet - please fix?] find out about the -state of the current branch on VMS. If the branch you're releasing on -is failing tests on VMS, you may not want to do a release. - =back =head2 Building a release - on the day @@ -389,8 +390,7 @@ unpushed commits etc): If not already built, Configure and build perl so that you have a Makefile and porting tools: - $ ./Configure -Dusedevel -des - $ make + $ ./Configure -Dusedevel -des && make =item * @@ -427,7 +427,7 @@ Commit META.yml if it has changed: I<You MUST SKIP this step for SNAPSHOT> -Update C<Module::Corelist>. +Update C<Module::Corelist> with module version data for the new release. Note that if this is a maint release, you should run the following actions from the maint directory, but commit the C<Corelist.pm> changes in @@ -444,6 +444,14 @@ Then change to your perl checkout, and if necessary, $ make perl +If this not the first update for this version, first edit +F<lib/Module/CoreList.pm>to delete the existing entries for this version +from the C<%released> and C<%version> hashes: they will have a key like +C<5.010001> for 5.10.1. + +XXX the edit-in-place functionality of Porting/corelist.pl should +be fixed to handle this automatically. + Then, If you have a local CPAN mirror, run: $ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror @@ -452,20 +460,14 @@ Otherwise, run: $ ./perl -Ilib Porting/corelist.pl cpan -This will chug for a while. Assuming all goes well, it will -update F<lib/Module/CoreList.pm>. +This will chug for a while, possibly reporting various warnings about +badly-indexed CPABN modules unreltaed to the modules actually in core. +Assuming all goes well, it will update F<lib/Module/CoreList.pm>. Check that file over carefully: $ git diff lib/Module/CoreList.pm -In particular, if this not the first update for this version, make sure -that there isn't a duplicated entry (e.g. '5.010001' entries for both RC1 -and RC2). - -XXX the edit-in-place functionality of Porting/corelist.pl should -be fixed to allow for this - If necessary, bump C<$VERSION> (there's no need to do this for every RC; in RC1, bump the version to a new clean number that will appear in the final release, and leave as-is for the later RCs and final). @@ -491,9 +493,7 @@ Finally, commit the new version of Module::CoreList: (unless this is for maint; in which case commit it blead first, then cherry-pick it back). - $ git commit -m 'Updated Module::CoreList for the 5.x.y release' \ - lib/Module/CoreList.pm - + $ git commit -m 'Update Module::CoreList for 5.x.y' lib/Module/CoreList.pm =item * @@ -502,6 +502,7 @@ Check that the manifest is sorted and correct: $ make manisort $ make distclean $ perl Porting/manicheck + $ git status Commit MANIFEST if it has changed: @@ -554,9 +555,19 @@ Build perl, then make sure it passes its own test suite, and installs: =item * -Check that the output of C<perl -v> and C<perl -V> are as expected, +Check that the output of C</tmp/perl-5.x.y-pretest/bin/perl -v> and +C</tmp/perl-5.x.y-pretest/bin/perl -V> are as expected, especially as regards version numbers, patch and/or RC levels, and @INC -paths. +paths. Note that as they have been been built from a git working +directory, they will still identify themselves using git tags and +commits. + +Then delete the temporary installation. + +=item * + +If this is maint release, make sure F<Porting/mergelog> is saved and +committed. =item * diff --git a/lib/Module/CoreList.pm b/lib/Module/CoreList.pm index 4661b36..e30d0aa 100644 --- a/lib/Module/CoreList.pm +++ b/lib/Module/CoreList.pm @@ -170,7 +170,7 @@ sub find_version { 5.009005 => '2007-07-07', 5.010000 => '2007-12-18', 5.008009 => '2008-12-14', - 5.010001 => '????-??-??', + 5.010001 => '2009-08-22', ); for my $version ( sort { $a <=> $b } keys %released ) { @@ -9500,7 +9500,7 @@ for my $version ( sort { $a <=> $b } keys %released ) { 'Pod::Text::Termcap' => '2.05', 'Pod::Usage' => '1.36', 'SDBM_File' => '1.06', - 'Safe' => '2.17_01', + 'Safe' => '2.18', 'Scalar::Util' => '1.21', 'Scalar::Util::PP' => '1.21', 'Search::Dict' => '1.02', diff --git a/pod/perlhist.pod b/pod/perlhist.pod index 5d84bf5..9512fd0 100644 --- a/pod/perlhist.pod +++ b/pod/perlhist.pod @@ -401,6 +401,7 @@ the strings?). 5.10.0 2007-Dec-18 David 5.10.1-RC1 2009-Aug-06 5.10.1-RC2 2009-Aug-18 + 5.10.1 2009-Aug-22 =head2 SELECTED RELEASE SIZES -- Perl5 Master Repository
