In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/c282dc5ebef25e8b002cd913928f847fab339716?hp=1802421e7ca37d5f22605a97946d04b9b2375b43>
- Log ----------------------------------------------------------------- commit c282dc5ebef25e8b002cd913928f847fab339716 Author: Abigail <[email protected]> Date: Fri Mar 25 13:36:28 2016 +0100 Suggest having the previous release ready. Each time I do a release, I find myself scrambling to download the tarball of the previous release, and install it so it can be compared to the release that's worked on. Added a paragraph as a reminder to that before the day of the release. ----------------------------------------------------------------------- Summary of changes: Porting/release_managers_guide.pod | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 1c82b26..6d67d0b 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -183,6 +183,13 @@ is only needed on the day of the release or shortly afterwards. You will need a quotation to use as an epigraph to your release announcement. +=head3 Install the previous version of perl + +During the testing phase of the release you have created, you will be +asked to compare the installed files with a previous install. Save yourself +some time on release day, and have a (clean) install of the previous +version ready. + =head2 Building a release - advance actions The work of building a release candidate for an even numbered release -- Perl5 Master Repository
