In perl.git, the branch maint-5.22 has been updated <http://perl5.git.perl.org/perl.git/commitdiff/b1e321e79b208c7ed925b1d9f59283bfb08bc625?hp=669c0c05ec87759a60850ebe8f5751f319834484>
- Log ----------------------------------------------------------------- commit b1e321e79b208c7ed925b1d9f59283bfb08bc625 Author: Father Chrysostomos <[email protected]> Date: Tue Sep 13 22:54:49 2016 -0700 perldelta for ba0a4150f (cherry picked from commit 5c0226f4301ebe0bbd5f2b351893c751547d35b4) M pod/perldelta.pod commit b3c27ae44b1203f917f413b84e6449a98ecd24ad Author: Stevan Little <[email protected]> Date: Fri Feb 24 08:32:20 2017 +0000 working on perldelta (manually cherry picked from commit 2c4879e2628d6fa5a764e130f610deaff6f859a5) M pod/perldelta.pod commit 5f08b6cf72f87ba8e08a3cc434ca95127e80f61d Author: James E Keenan <[email protected]> Date: Fri Dec 30 09:58:17 2016 -0500 Discuss Porting/sync-with-cpan -- the simpler usage -- first. Incorporate feedback from Aaron Crane. (cherry picked from commit b58fbdf5435d95b4f46a14e4da3b782dfb46b1cb) M Porting/release_managers_guide.pod commit 788fb9bc922dbad6e57fde02d21b7a0b650d31ac Author: Aaron Crane <[email protected]> Date: Fri Nov 11 12:01:24 2016 +0100 RMG: suggest a simpler way of reviewing perlhist changes (cherry picked from commit c26b8729ead2f4443204c497f98dc3767fca205f) M Porting/release_managers_guide.pod commit 722fa1ced5f207e08c5c0d11e44f141d3b67ce4c Author: Aaron Crane <[email protected]> Date: Fri Nov 11 11:54:52 2016 +0100 RMG: break a list over multiple lines I found these three similar filenames hard to read when flowed into a single paragraph. (cherry picked from commit 77087aae3c818e7cc72eaa85f8005396c5addd5e) M Porting/release_managers_guide.pod commit 16cbaf33da5539bf069f8bb9a2d40a6a77378777 Author: reneeb <[email protected]> Date: Fri Feb 24 08:17:14 2017 +0000 finalize perldelta (manually cherry picked from commit 4b99a68c34a1cfc3a4769459a7d93a36acae8219) M pod/perlhist.pod commit 84754568ba670ae61f4ccbe12699301765fcbbf4 Author: Abigail <[email protected]> Date: Fri Jan 20 04:07:32 2017 +0100 Let's be consistent (cherry picked from commit 5d577b6f636aba916a1b0519669de4b2454c68ab) M pod/perlhist.pod commit 0d861a9649e83227d4ea69b8291596e1aef2dbbd Author: Abigail <[email protected]> Date: Fri Jan 20 04:06:13 2017 +0100 Add perlhist entry for the 5.25.9 release (cherry picked from commit 4bbbe3d9235093a7de0bbedb3aa9c8b57feb2fe0) M pod/perlhist.pod ----------------------------------------------------------------------- Summary of changes: Porting/release_managers_guide.pod | 49 ++++++++++++++++++++++++++------------ pod/perldelta.pod | 12 ++++++++-- pod/perlhist.pod | 6 +++-- 3 files changed, 48 insertions(+), 19 deletions(-) diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 56b8847ec2..86f5e41c38 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -245,6 +245,15 @@ have some extra changes. =head3 How to sync a CPAN module with a cpanE<sol> distro +In most cases, once a new version of a distribution shipped with core has been +uploaded to CPAN, the core version thereof can be synchronized automatically +with the program F<Porting/sync-with-cpan>. (But see the comments at the +beginning of that program. In particular, it has not yet been exercised on +Windows as much as it has on Unix-like platforms.) + +If, however, F<Porting/sync-with-cpan> does not provide good results, follow +the steps below. + =over 4 =item * @@ -326,12 +335,6 @@ If everything is ok, commit the changes. For entries with a non-simple C<FILES> section, or with a C<MAP>, you may have to take more steps than listed above. -F<Porting/sync-with-cpan> is a script that automates most of the steps -above; but see the comments at the beginning of the file. In particular, -it has not yet been exercised on Windows, but will certainly require a set -of Unix tools such as Cygwin, and steps that run C<make> will need to run -C<nmake> instead. - =head3 dual-life CPAN module stability Ensure dual-life CPAN modules are stable, which comes down to: @@ -597,9 +600,23 @@ C<$Module::CoreList::Utils::VERSION> should always be equal to C<$Module::CoreList::VERSION>. If necessary, bump those two versions to match before proceeding. -The files to modify are: F<dist/Module-CoreList/lib/Module/CoreList.pm>, -F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm> and -F<dist/Module-CoreList/lib/Module/CoreList/TieHashDelta.pm>. +The files to modify are: + +=over 4 + +=item * + +F<dist/Module-CoreList/lib/Module/CoreList.pm> + +=item * + +F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm> + +=item * + +F<dist/Module-CoreList/lib/Module/CoreList/TieHashDelta.pm> + +=back =head4 Update C<Module::CoreList> with module version data for the new release. @@ -793,12 +810,14 @@ then configure and build perl so that you have a Makefile and porting tools: For the first RC for a MAINT release, copy in the latest F<pod/perlhist.pod> from blead; this will include details of newer releases in all branches. In theory, blead's version should be a strict -superset of the one in this branch, but it's probably safest to diff them -first to ensure that there's nothing in this branch that was forgotten -from blead: - - $ diff pod/perlhist.pod ..../blead/pod/perlhist.pod - $ cp ..../blead/pod/perlhist.pod pod/ +superset of the one in this branch, but it's probably safest to examine the +changes first, to ensure that there's nothing in this branch that was +forgotten from blead. An easy way to do that is with C<< git checkout -p >>, +to selectively apply any changes from the blead version to your current +branch: + + $ git fetch origin + $ git checkout -p origin/blead pod/perlhist.pod $ git commit -m 'sync perlhist from blead' pod/perlhist.pod =head3 update perlhist.pod diff --git a/pod/perldelta.pod b/pod/perldelta.pod index caad8ab002..fe77b2596b 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -33,7 +33,14 @@ XXX Any security-related notices go here. In particular, any security vulnerabilities closed should be noted here rather than in the L</Selected Bug Fixes> section. -[ List each security issue as a =head2 entry ] +=head2 "Escaped" colons and relative paths in PATH + +On Unix systems, Perl treats any relative paths in the PATH environment +variable as tainted when starting a new process. Previously, it was +allowing a backslash to escape a colon (unlike the OS), consequently +allowing relative paths to be considered safe if the PATH was set to +something like C</\:.>. The check has been fixed to treat C<.> as tainted +in that example. =head1 Incompatible Changes @@ -358,7 +365,8 @@ platform specific bugs also go here. =item * -XXX +Fixed a crash with C<s///l> where it thought it was dealing with UTF-8 +when it wasn't. [perl #129038] =back diff --git a/pod/perlhist.pod b/pod/perlhist.pod index 1b2e626bc8..dfb3b2c8a5 100644 --- a/pod/perlhist.pod +++ b/pod/perlhist.pod @@ -33,7 +33,7 @@ Matt S Trout, David Golden, Florian Ragwitz, Tatsuhiko Miyagawa, Chris C<BinGOs> Williams, Zefram, Ãvar Arnfjörð Bjarmason, Stevan Little, Dave Rolsky, Max Maischein, Abigail, Jesse Luehrs, Tony Cook, Dominic Hargreaves, Aaron Crane, Aristotle Pagaltzis, Matthew Horsfall, -Peter Martini, Sawyer X, and Chad 'Exodist' Granum. +Peter Martini, Sawyer X, Chad 'Exodist' Granum, and Renee Bäcker. =head2 PUMPKIN? @@ -606,7 +606,9 @@ the strings?). Stevan 5.25.5 2016-Sep-20 Aaron 5.25.6 2016-Oct-20 Chad 5.25.7 2016-Nov-20 - Sawyer 5.25.8 2016-Dec-20 + Sawyer X 5.25.8 2016-Dec-20 + Abigail 5.25.9 2017-Jan-20 + Renee 5.25.10 2017-Feb-20 =head2 SELECTED RELEASE SIZES -- Perl5 Master Repository
