5 release_managers_guide - Releasing a new version of perl 5.x
7 Note that things change at each release, so there may be new things not
8 covered here, or tools may need updating.
10 =head1 MAKING A CHECKLIST
12 If you are preparing to do a release, you can run the
13 F<Porting/make-rmg-checklist> script to generate a new version of this
14 document that starts with a checklist for your release.
16 This script is run as:
18 perl Porting/make-rmg-checklist \
19 --version [5.x.y-RC#] > /tmp/rmg.pod
21 You can also pass the C<--html> flag to generate an HTML document instead of
24 perl Porting/make-rmg-checklist --html \
25 --version [5.x.y-RC#] > /tmp/rmg.html
29 This document describes the series of tasks required - some automatic, some
30 manual - to produce a perl release of some description, be that a release
31 candidate, or final, numbered release of maint or blead.
33 New releases of perl are made each month on the 20th by a release engineer
34 appointed by the Steering Council. The release engineer roster and schedule
35 can be found in Porting/release_schedule.pod.
37 This document both helps as a check-list for the release engineer
38 and is a base for ideas on how the various tasks could be automated
41 The checklist of a typical release cycle is as follows:
43 (5.10.1 is released, and post-release actions have been done)
47 a few weeks before the release, a number of steps are performed,
48 including bumping the version to 5.10.2
50 ...a few weeks pass...
52 perl-5.10.2-RC1 is released
54 perl-5.10.2 is released
56 post-release actions are performed, including creating new
59 ... the cycle continues ...
63 Some of the tasks described below apply to all four types of
64 release of Perl. (blead, RC, final release of maint, final
65 release of blead). Some of these tasks apply only to a subset
66 of these release types. If a step does not apply to a given
67 type of release, you will see a notation to that effect at
68 the beginning of the step.
70 This guide assumes you are working on the Perl master repository (i.e.
71 L<https://github.com/Perl/perl5>) and B<not> on your own fork of the perl5
72 repository. While it is possible to prepare a release on your own fork
73 this guide is not written with that in mind and as a result several
74 key steps are missing. If you do use your own fork then extra care
75 needs to be taken when setting/pushing the tag and doing the merge
82 =item Release Candidate (RC)
84 A release candidate is an attempt to produce a tarball that is a close as
85 possible to the final release. Indeed, unless critical faults are found
86 during the RC testing, the final release will be identical to the RC
87 barring a few minor fixups (updating the release date in F<perlhist.pod>,
88 removing the RC status from F<patchlevel.h>, etc). If faults are found,
89 then the fixes should be put into a new release candidate, never directly
93 =item Stable/Maint release (MAINT).
95 A release with an even version number, and subversion number > 0, such as
98 At this point you should have a working release candidate with few or no
101 It's essentially the same procedure as for making a release candidate, but
102 with a whole bunch of extra post-release steps.
104 Note that for a maint release there are two versions of this guide to
105 consider: the one in the maint branch, and the one in blead. Which one to
106 use is a fine judgement. The blead one will be most up-to-date, while
107 it might describe some steps or new tools that aren't applicable to older
108 maint branches. It is probably best to review both versions of this
109 document, but to most closely follow the steps in the maint version.
111 =item A blead point release (BLEAD-POINT)
113 A release with an odd version number, such as 5.15.0 or 5.15.1.
115 This isn't for production, so it has less stability requirements than for
116 other release types, and isn't preceded by RC releases. Other than that,
117 it is similar to a MAINT release.
119 =item Blead final release (BLEAD-FINAL)
121 A release with an even version number, and subversion number == 0, such as
122 5.14.0. That is to say, it's the big new release once per year.
124 It's essentially the same procedure as for making a release candidate, but
125 with a whole bunch of extra post-release steps, even more than for MAINT.
133 Before you can make an official release of perl, there are a few
134 hoops you need to jump through:
136 =head3 PAUSE account with pumpkin status
138 Make sure you have a PAUSE account suitable for uploading a perl release.
139 If you don't have a PAUSE account, then request one:
141 https://pause.perl.org/pause/query?ACTION=request_id
143 Check that your account is allowed to upload perl distros: go to
144 L<https://pause.perl.org/pause/authenquery?ACTION=who_pumpkin> and check that
145 your PAUSE ID is listed there. If not, ask Andreas KE<0xf6>nig to add your ID
146 to the list of people allowed to upload something called perl. You can find
147 Andreas' email address at:
149 https://pause.perl.org/pause/query?ACTION=pause_04imprint
153 You will need a working C<git> installation, checkout of the perl
154 git repository and perl commit bit. For information about working
155 with perl and git, see L<perlgit>.
157 If you are not yet a perl committer, you won't be able to make a
158 release. You will need to have a GitHub account (if you don't have one)
159 and contact the Steering Council with your username to get membership in the
160 L<< Perl-Releasers|https://github.com/orgs/Perl/teams/perl-releasers >> team.
162 =head3 web-based file share
164 You will need to be able to share tarballs with #p5p members for
165 pre-release testing, and you may wish to upload to PAUSE via URL.
166 Make sure you have a way of sharing files, such as a web server or
167 file-sharing service.
169 If you use Dropbox, you can append "raw=1" as a parameter to their usual
170 sharing link to allow direct download (albeit with redirects).
172 =head3 Quotation for release announcement epigraph
174 You will need a quotation to use as an epigraph to your release announcement.
175 It will live forever (along with Perl), so make it a good one.
177 =head3 Install the previous version of perl
179 During the testing phase of the release you have created, you will be
180 asked to compare the installed files with a previous install. Save yourself
181 some time on release day, and have a (clean) install of the previous
184 =head3 Email account subscribed to perl5-porters
186 In order for your release announcement email to be delivered to the
187 perl5-porters distribution list, the email address that you intend to
188 send from must be subscribed to the list.
190 Instructions for subscribing can be found here:
191 L<List: perl5-porters|https://lists.perl.org/list/perl5-porters.html>
193 =head2 Building a release - advance actions
195 The work of building a release candidate for an even numbered release
196 (BLEAD-FINAL) of perl generally starts several weeks before the first
197 release candidate. Some of the following steps should be done regularly,
198 but all I<must> be done in the run up to a release.
200 =head3 dual-life CPAN module synchronisation
202 To see which core distro versions differ from the current CPAN versions:
204 $ ./perl -Ilib Porting/core-cpan-diff -x -a
206 However, this only checks whether the version recorded in
207 F<Porting/Maintainers.pl> differs from the latest on CPAN. It doesn't tell you
208 if the code itself has diverged from CPAN.
210 You can also run an actual diff of the contents of the modules, comparing core
211 to CPAN, to ensure that there were no erroneous/extraneous changes that need to
212 be dealt with. You do this by not passing the C<-x> option:
214 $ ./perl -Ilib Porting/core-cpan-diff -a -o ~/corediffs
216 Passing C<-u cpan> will probably be helpful, since it limits the search to
217 distributions with 'cpan' upstream source. (It's OK for blead upstream to
218 differ from CPAN because those dual-life releases usually come I<after> perl
221 See also the C<-d> and C<-v> options for more detail (and the C<-u> option as
222 mentioned above). You'll probably want to use the C<-c cachedir> option to
223 avoid repeated CPAN downloads and may want to use C<-m file:///mirror/path> if
224 you made a local CPAN mirror. Note that a minicpan mirror won't actually work,
225 but can provide a good first pass to quickly get a list of modules which
226 definitely haven't changed, to avoid having to download absolutely everything.
228 For a BLEAD-POINT or BLEAD-FINAL release with 'cpan' upstream, if a CPAN
229 release appears to be ahead of blead, then consider updating it (or asking the
230 relevant porter to do so). (However, if this is a BLEAD-FINAL release or one of
231 the last BLEAD-POINT releases before it and hence blead is in some kind of
232 "code freeze" state (e.g. the sequence might be "contentious changes freeze",
233 then "user-visible changes freeze" and finally "full code freeze") then any
234 CPAN module updates must be subject to the same restrictions, so it may not be
235 possible to update all modules until after the BLEAD-FINAL release.) If blead
236 contains edits to a 'cpan' upstream module, this is naughty but sometimes
237 unavoidable to keep blead tests passing. Make sure the affected file has a
238 CUSTOMIZED entry in F<Porting/Maintainers.pl>.
240 If you are making a MAINT release, run C<core-cpan-diff> on both blead and
241 maint, then diff the two outputs. Compare this with what you expect, and if
242 necessary, fix things up. For example, you might think that both blead
243 and maint are synchronised with a particular CPAN module, but one might
244 have some extra changes.
246 In any case, any cpan-first distribution that is listed as having files
247 "Customized for blead" in the output of cpan-core-diff should have requests
248 submitted to the maintainer(s) to make a cpan release to catch up with blead.
250 Additionally, all files listed as "modified" but not "customized for blead"
251 should have entries added under the C<CUSTOMIZED> key in
252 F<Porting/Maintainers.pl>, as well as checksums updated via:
254 cd t; ../perl -I../lib porting/customized.t --regen
256 =head4 Sync CPAN modules with the corresponding cpanE<sol> distro
258 In most cases, once a new version of a distribution shipped with core has been
259 uploaded to CPAN, the core version thereof can be synchronized automatically
260 with the program F<Porting/sync-with-cpan>. (But see the comments at the
261 beginning of that program. In particular, it has not yet been exercised on
262 Windows as much as it has on Unix-like platforms.)
264 If, however, F<Porting/sync-with-cpan> does not provide good results, follow
271 Fetch the most recent version from CPAN.
275 Unpack the retrieved tarball. Rename the old directory; rename the new
276 directory to the original name.
280 Restore any F<.gitignore> file. This can be done by issuing
281 C<git checkout .gitignore> in the F<cpan/Distro> directory.
285 Remove files we do not need. That is, remove any files that match the
286 entries in C<@IGNORABLE> in F<Porting/Maintainers.pl>, and anything that
287 matches the C<EXCLUDED> section of the distro's entry in the C<%Modules>
292 Restore any files mentioned in the C<CUSTOMIZED> section, using
293 C<git checkout>. Make any new customizations if necessary. Also,
294 restore any files that are mentioned in C<@IGNORE>, but were checked
295 into the repository anyway.
299 For any new files in the distro, determine whether they are needed.
300 If not, delete them, and list them in either C<EXCLUDED> or C<@IGNORABLE>.
301 Otherwise, add them to C<MANIFEST>, and run C<git add> to add the files
306 For any files that are gone, remove them from C<MANIFEST>, and use
307 C<git rm> to tell git the files will be gone.
311 If the C<MANIFEST> file was changed in any of the previous steps, run
312 C<perl Porting/manisort --output MANIFEST.sort; mv MANIFEST.sort MANIFEST>.
316 For any files that have an execute bit set, either remove the execute
317 bit, or edit F<Porting/exec-bit.txt>
321 Run C<make> (or C<nmake> on Windows), see if C<perl> compiles.
325 Run the tests for the package.
329 Run the tests in F<t/porting> (C<make test_porting>).
333 Update the C<DISTRIBUTION> entry in F<Porting/Maintainers.pl>.
337 Run a full configure/build/test cycle.
341 If everything is ok, commit the changes.
345 For entries with a non-simple C<FILES> section, or with a C<MAP>, you
346 may have to take more steps than listed above.
348 =head3 Ensure dual-life CPAN module stability
352 for each module that fails its regression tests on $current
353 did it fail identically on $previous?
354 if yes, "SEP" (Somebody Else's Problem, but try to make sure a
356 else work out why it failed (a bisect is useful for this)
358 attempt to group failure causes
360 for each failure cause
361 is that a regression?
362 if yes, figure out how to fix it
363 (more code? revert the code that broke it)
365 (presumably) it's relying on something un-or-under-documented
366 should the existing behaviour stay?
367 yes - goto "regression"
368 no - note it in perldelta as a significant bugfix
369 (also, try to inform the module's author)
371 =head3 monitor smoke tests for failures
373 Similarly, monitor the smoking of core tests, and try to fix. See
374 L<https://tux.nl/perl5/smoke/index.html>, L<https://perl5.test-smoke.org/>
375 and L<http://perl.develop-help.com> for a summary. See also
376 L<https://www.nntp.perl.org/group/perl.daily-build.reports/> which has
379 Similarly, monitor the smoking of perl for compiler warnings, and try to
382 Additionally both L<Travis CI|https://travis-ci.org/Perl/perl5> and
383 L<GitHub Actions|https://github.com/Perl/perl5/actions> smokers run
386 =for checklist skip BLEAD-POINT
388 =head3 monitor CPAN testers for failures
390 For any release except a BLEAD-POINT: Examine the relevant analysis report(s)
391 at L<http://analysis.cpantesters.org/beforemaintrelease> to see how the
392 impending release is performing compared to previous releases with
393 regard to building and testing CPAN modules.
395 That page accepts a query parameter, C<pair> that takes a pair of
396 colon-delimited versions to use for comparison. For example:
398 L<http://analysis.cpantesters.org/beforemaintrelease?pair=5.20.2:5.22.0%20RC1>
400 =head3 update perldelta
402 Get perldelta in a mostly finished state.
404 Read F<Porting/how_to_write_a_perldelta.pod>, and try to make sure that
405 every section it lists is, if necessary, populated and complete. Copy
406 edit the whole document.
408 You won't be able to automatically fill in the "Updated Modules" section until
409 after Module::CoreList is updated (as described below in
410 L<"update Module::CoreList">).
412 =head3 Bump the version number
414 Do not do this yet for a BLEAD-POINT release! You will do this at the end of
415 the release process (after building the final tarball, tagging etc).
417 Increase the version number (e.g. from 5.12.0 to 5.12.1).
419 For a release candidate for a stable perl, this should happen a week or two
420 before the first release candidate to allow sufficient time for testing and
421 smoking with the target version built into the perl executable. For
422 subsequent release candidates and the final release, it is not necessary to
423 bump the version further.
425 There is a tool to semi-automate this process:
427 $ ./perl -Ilib Porting/bump-perl-version -i 5.10.0 5.10.1
429 Remember that this tool is largely just grepping for '5.10.0' or whatever,
430 so it will generate false positives. Be careful not change text like
431 "this was fixed in 5.10.0"!
433 Use git status and git diff to select changes you want to keep.
435 Be particularly careful with F<INSTALL>, which contains a mixture of
436 C<5.10.0>-type strings, some of which need bumping on every release, and
437 some of which need to be left unchanged.
438 See below in L<"update INSTALL"> for more details.
440 For the first RC release leading up to a BLEAD-FINAL release, update the
441 description of which releases are now "officially" supported in
442 F<pod/perlpolicy.pod>.
444 When doing a BLEAD-POINT or BLEAD-FINAL release, also make sure the
445 C<PERL_API_*> constants in F<patchlevel.h> are in sync with the version
446 you're releasing, unless you're absolutely sure the release you're about to
447 make is 100% binary compatible to an earlier release. Note: for BLEAD-POINT
448 releases the bump should have already occurred at the end of the previous
449 release and this is something you would have to do at the very end.
450 When releasing a MAINT perl version, the C<PERL_API_*> constants C<MUST NOT>
451 be changed as we aim to guarantee binary compatibility in maint branches.
453 After editing, regenerate uconfig.h (this must be run on a system with a
456 $ perl regen/uconfig_h.pl
458 This might not cause any new changes.
460 You may also need to regen opcodes:
462 $ ./perl -Ilib regen/opcode.pl
466 $ git clean -xdf # careful if you don't have local files to keep!
467 $ ./Configure -des -Dusedevel
471 Do note that at this stage, porting tests will fail. They will continue
472 to fail until you've updated Module::CoreList, as described below.
478 B<review the delta carefully>
480 $ git commit -a -m 'Bump the perl version in various places for 5.x.y'
482 At this point you may want to compare the commit with a previous bump to
483 see if they look similar. See commit f7cf42bb69 for an example of a
484 previous version bump.
486 When the version number is bumped, you should also update Module::CoreList
487 (as described below in L<"update Module::CoreList">) to reflect the new
490 =head3 update INSTALL
492 Review and update INSTALL to account for the change in version number.
493 INSTALL for a BLEAD-POINT release should already contain the expected version.
494 The lines in F<INSTALL> about "is not binary compatible with" may require a
495 correct choice of earlier version to declare incompatibility with. These are
496 in the "Changes and Incompatibilities" and "Coexistence with earlier versions
499 Be particularly careful with the section "Upgrading from 5.X.Y or earlier".
500 The "X.Y" needs to be changed to the most recent version that we are
501 I<not> binary compatible with.
503 For MAINT and BLEAD-FINAL releases, this needs to refer to the last
504 release in the previous development cycle (so for example, for a 5.14.x
505 release, this would be 5.13.11).
507 For BLEAD-POINT releases, it needs to refer to the previous BLEAD-POINT
508 release (so for 5.15.3 this would be 5.15.2). If the last release manager
509 followed instructions, this should have already been done after the last
510 blead release, so you may find nothing to do here.
512 =head3 update AUTHORS
514 The AUTHORS file can be updated by running F<Porting/updateAUTHORS.pl>.
515 This shouldn't really be necessary anymore, and in theory nothing should
516 change as our CI should not pass if a commit would result in AUTHORS
517 needing to change, but do it anyway to be sure. Make sure all your changes
520 Review the changes to the AUTHORS file, be sure you are not adding duplicate
521 entries or removing any entries, then commit your changes.
523 $ git commit -a AUTHORS -m 'Update AUTHORS list for 5.x.y'
525 =head3 Check copyright years
527 Check that the copyright years are up to date by running:
529 $ pushd t; ../perl -I../lib porting/copyright.t --now
531 Remedy any test failures by editing README or perl.c accordingly (search for
532 the "Copyright"). If updating perl.c, check if the file's own copyright date in
533 the C comment at the top needs updating, as well as the one printed by C<-v>.
535 =head3 Check more build configurations
537 Try running the full test suite against multiple Perl configurations. Here are
538 some sets of Configure flags you can try:
544 C<-Duseshrplib -Dusesitecustomize>
548 C<-Duserelocatableinc>
556 If you have multiple compilers on your machine, you might also consider
557 compiling with C<-Dcc=$other_compiler>.
559 You can also consider pushing the repo to GitHub where Travis CI is enabled
560 which would smoke different flavors of Perl for you.
562 =head3 update perlport
564 L<perlport> has a section currently named I<Supported Platforms> that
565 indicates which platforms are known to build in the current release.
566 If necessary update the list and the indicated version number.
568 =head3 check a readonly build
570 Even before other prep work, follow the steps in L</build the tarball> and test
571 it locally. Because a perl source tarballs sets many files read-only, it could
572 test differently than tests run from the repository. After you're sure
573 permissions aren't a problem, delete the generated directory and tarballs.
576 =head2 Building a release - on the day
578 This section describes the actions required to make a release
579 that are performed near to, or on the actual release day.
581 =head3 re-check earlier actions
583 Review all the actions in the previous section,
584 L<"Building a release - advance actions"> to ensure they are all done and
587 =head3 create a release branch
589 For BLEAD-POINT releases, making a release from a release branch avoids the
590 need to freeze blead during the release. This is less important for
591 BLEAD-FINAL, MAINT, and RC releases, since blead will already be frozen in
592 those cases. Create the branch by running
594 git checkout -b release-5.xx.yy
596 =head3 build a clean perl
598 Make sure you have a gitwise-clean perl directory (no modified files,
599 unpushed commits etc):
604 then configure and build perl so that you have a Makefile and porting tools:
606 $ ./Configure -Dusedevel -des && make
608 =head3 Check module versions
610 For each Perl release since the previous release of the current branch, check
611 for modules that have identical version numbers but different contents by
614 $ ./perl -Ilib Porting/cmpVERSION.pl --tag=v5.X.YY
616 (This is done automatically by F<t/porting/cmp_version.t> for the previous
617 release of the current branch, but not for any releases from other branches.)
619 Any modules that fail will need a version bump, plus a nudge to the upstream
620 maintainer for 'cpan' upstream modules.
622 =head3 update Module::CoreList
624 =head4 Bump Module::CoreList* $VERSIONs
626 If necessary, bump C<$VERSION> (there's no need to do this
627 for every RC; in RC1, bump the version to a new clean number that will
628 appear in the final release, and leave as-is for the later RCs and final).
629 It may also happen that C<Module::CoreList> has been modified in blead, and
630 hence has a new version number already. (But make sure it is not the same
631 number as a CPAN release.)
633 C<$Module::CoreList::Utils::VERSION> should always be equal to
634 C<$Module::CoreList::VERSION>. If necessary, bump those two versions to match
637 Once again, the files to modify are:
643 F<dist/Module-CoreList/lib/Module/CoreList.pm>
647 F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm>
651 =head4 Update C<Module::CoreList> with module version data for the new release.
653 Note that if this is a MAINT release, you should run the following actions
654 from the maint branch, but commit the C<CoreList.pm> changes in
655 I<blead> and subsequently cherry-pick any releases since the last
656 maint release and then your recent commit. XXX need a better example
658 [ Note that the procedure for handling Module::CoreList in maint branches
659 is a bit complex, and the RMG currently don't describe a full and
660 workable approach. The main issue is keeping Module::CoreList
661 and its version number synchronised across all maint branches, blead and
662 CPAN, while having to bump its version number for every RC release.
663 See this brief p5p thread:
665 Message-ID: <20130311174402.GZ2294@iabyn.com>
667 If you can devise a workable system, feel free to try it out, and to
668 update the RMG accordingly!
672 F<corelist.pl> uses www.cpan.org to verify information about dual-lived
673 modules on CPAN. It can use a full, local CPAN mirror and/or fall back
674 on HTTP::Tiny to fetch package metadata remotely.
676 (If you'd prefer to have a full CPAN mirror, see
677 L<https://www.cpan.org/misc/cpan-faq.html#How_mirror_CPAN>)
679 Change to your perl checkout, and if necessary,
683 Then, If you have a local CPAN mirror, run:
685 $ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror
689 $ ./perl -Ilib Porting/corelist.pl cpan
691 This will chug for a while, possibly reporting various warnings about
692 badly-indexed CPAN modules unrelated to the modules actually in core.
693 Assuming all goes well, it will update
694 F<dist/Module-CoreList/lib/Module/CoreList.pm> and possibly
695 F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm>.
697 Check those files over carefully:
699 $ git diff dist/Module-CoreList/lib/Module/CoreList.pm
700 $ git diff dist/Module-CoreList/lib/Module/CoreList/Utils.pm
702 =head4 Bump version in Module::CoreList F<Changes>
704 Also edit Module::CoreList's new version number in its F<Changes> file.
705 This file is F<dist/Module-CoreList/Changes>.
706 (BLEAD-POINT releases should have had this done already as a post-release
707 action from the last commit.)
709 =head4 Add Module::CoreList version bump to perldelta
711 Add a perldelta entry for the new Module::CoreList version. You only
712 need to do this if you want to add notes about the changes included
713 with this version of Module::CoreList. Otherwise, its version bump
714 will be automatically filled in below in L</finalize perldelta>.
716 =for checklist skip RC
718 =head4 Update C<%Module::CoreList::released>
720 For any release except an RC: Update this version's entry in the C<%released>
721 hash with today's date.
723 =head4 Commit Module::CoreList changes
725 Finally, commit the new version of Module::CoreList:
726 (unless this is for MAINT; in which case commit it to blead first, then
727 cherry-pick it back).
729 $ git commit -m 'Update Module::CoreList for 5.x.y' \
730 dist/Module-CoreList/Changes \
731 dist/Module-CoreList/lib/Module/CoreList.pm \
732 dist/Module-CoreList/lib/Module/CoreList/Utils.pm
734 =head4 Rebuild and test
736 Build and test to get the changes into the currently built lib directory and to
737 ensure all tests are passing.
739 =head3 finalize perldelta
741 Finalize the perldelta. In particular, fill in the Acknowledgements
742 section, which can be generated with something like:
744 $ perl Porting/acknowledgements.pl v5.15.0..HEAD
746 Fill in the "New/Updated Modules" sections now that Module::CoreList is
749 $ ./perl -Ilib Porting/corelist-perldelta.pl \
750 --mode=update pod/perldelta.pod
752 For a MAINT release use something like this instead:
754 $ ./perl -Ilib Porting/corelist-perldelta.pl 5.020001 5.020002 \
755 --mode=update pod/perldelta.pod
757 Ideally, also fill in a summary of the major changes to each module for which
758 an entry has been added by F<corelist-perldelta.pl>.
760 Re-read the perldelta to try to find any embarrassing typos and thinkos;
761 remove any C<TODO> or C<XXX> flags; update the "Known Problems" section
762 with any serious issues for which fixes are not going to happen now; and
763 run through pod and spell checkers, e.g.
765 $ podchecker -warnings -warnings pod/perldelta.pod
766 $ spell pod/perldelta.pod
767 $ aspell list < pod/perldelta.pod | sort -u
769 Also, you may want to generate and view an HTML version of it to check
772 $ ./perl -Ilib ext/Pod-Html/bin/pod2html pod/perldelta.pod > \
775 You should add pod links for GitHub issue references thusly:
777 $ perl -p -i -e'BEGIN{undef $/}; s{(GH\s+#)(\d+)}{L<$1$2|https://github.com/Perl/perl5/issues/$2>}mg' pod/perldelta.pod
779 If you make changes, be sure to commit them.
781 =for checklist skip BLEAD-POINT MAINT RC
783 =head3 remove stale perldeltas
785 For the first RC release that is ONLY for a BLEAD-FINAL, the perldeltas
786 from the BLEAD-POINT releases since the previous BLEAD-FINAL should have
787 now been consolidated into the current perldelta, and hence are now just
788 useless clutter. They can be removed using:
790 $ git rm <file1> <file2> ...
792 For example, for RC0 of 5.16.0:
795 $ git rm perldelta515*.pod
797 =for checklist skip BLEAD-FINAL BLEAD-POINT
799 =head3 add recent perldeltas
801 For the first RC for a MAINT release, copy in any recent perldeltas from
802 blead that have been added since the last release on this branch. This
803 should include any recent maint releases on branches older than your one,
804 but not newer. For example if you're producing a 5.14.x release, copy any
805 perldeltas from recent 5.10.x, 5.12.x etc maint releases, but not from
806 5.16.x or higher. Remember to
808 $ git add <file1> <file2> ...
810 =head3 update and commit perldelta files
812 If you have added or removed any perldelta files via the previous two
813 steps, then edit F<pod/perl.pod> to add/remove them from its table of
814 contents, then run F<Porting/pod_rules.pl> to propagate your changes there
815 into all the other files that mention them (including F<MANIFEST>). You'll
816 need to C<git add> the files that it changes.
818 Then build a clean perl and do a full test
822 $ ./Configure -Dusedevel -des
826 Once all tests pass, commit your changes.
828 =head3 final check of perldelta placeholders
830 Check for any 'XXX' leftover section in the perldelta.
831 Either fill them or remove these sections appropriately.
833 $ git grep XX pod/perldelta.pod
835 =head3 build a clean perl
837 If you skipped the previous step (adding/removing perldeltas),
838 again, make sure you have a gitwise-clean perl directory (no modified files,
839 unpushed commits etc):
844 then configure and build perl so that you have a Makefile and porting tools:
846 $ ./Configure -Dusedevel -des && make
848 =for checklist skip BLEAD-FINAL BLEAD-POINT
850 =head3 synchronise from blead's perlhist.pod
852 For the first RC for a MAINT release, copy in the latest
853 F<pod/perlhist.pod> from blead; this will include details of newer
854 releases in all branches. In theory, blead's version should be a strict
855 superset of the one in this branch, but it's probably safest to examine the
856 changes first, to ensure that there's nothing in this branch that was
857 forgotten from blead. An easy way to do that is with C<< git checkout -p >>,
858 to selectively apply any changes from the blead version to your current
862 $ git checkout -p origin/blead pod/perlhist.pod
863 $ git commit -m 'Sync perlhist from blead' pod/perlhist.pod
865 =head3 update perlhist.pod
867 Add an entry to F<pod/perlhist.pod> with the release date, e.g.:
869 David 5.10.1 2009-Aug-06
871 List yourself in the left-hand column, and if this is the first release
872 that you've ever done, make sure that your name is listed in the section
873 entitled C<THE KEEPERS OF THE PUMPKIN>.
875 I<If you're making a BLEAD-FINAL release>, also update the "SELECTED
876 RELEASE SIZES" section with the output of
877 F<Porting/perlhist_calculate.pl>.
879 Be sure to commit your changes:
881 $ git commit -m 'Add new release to perlhist' pod/perlhist.pod
883 =for checklist skip BLEAD-POINT
885 =head3 update patchlevel.h
887 I<You MUST SKIP this step for a BLEAD-POINT release>
889 Update F<patchlevel.h> to add a C<-RC1>-or-whatever string; or, if this is
890 a final release, remove it. For example:
892 static const char * const local_patches[] = {
895 #ifdef PERL_GIT_UNCOMMITTED_CHANGES
896 ,"uncommitted-changes"
899 Be sure to commit your change:
901 $ git commit -m 'Bump version to RCnnn' patchlevel.h
903 =head3 run makemeta to update META files
905 $ ./perl -Ilib Porting/makemeta
907 Be sure to commit any changes (if applicable):
909 $ git status # any changes?
910 $ git commit -m 'Update META files' META.*
912 =head3 build, test and check a fresh perl
914 Build perl, then make sure it passes its own test suite, and installs:
917 $ ./Configure -des -Dprefix=/tmp/perl-5.x.y-pretest
919 # or if it's an odd-numbered version:
920 $ ./Configure -des -Dusedevel -Dprefix=/tmp/perl-5.x.y-pretest
924 Check that the output of C</tmp/perl-5.x.y-pretest/bin/perl -v> and
925 C</tmp/perl-5.x.y-pretest/bin/perl -V> are as expected,
926 especially as regards version numbers, patch and/or RC levels, and @INC
927 paths. Note that as they have been built from a git working
928 directory, they will still identify themselves using git tags and
929 commits. (Note that for an odd-numbered version, perl will install
930 itself as C<perl5.x.y>). C<perl -v> will identify itself as:
932 This is perl 5, version X, subversion Y (v5.X.Y (v5.X.Z-NNN-gdeadbeef))
934 where 5.X.Z is the latest tag, NNN the number of commits since this tag,
935 and C<< deadbeef >> commit of that tag.
937 Then delete the temporary installation.
939 =head3 create the release tag
941 Create the tag identifying this release (e.g.):
943 $ git tag v5.11.0 -m 'First release of the v5.11 series!'
945 It is B<VERY> important that from this point forward, you not push
946 your git changes to the Perl master repository. If anything goes
947 wrong before you publish your newly-created tag, you can delete
948 and recreate it. Once you push your tag, we're stuck with it
949 and you'll need to use a new version number for your release.
951 =head3 build the tarball
953 Before you run the following, you might want to install 7-Zip (the
954 C<p7zip-full> package under Debian or the C<p7zip> port on MacPorts) or
955 the AdvanceCOMP suite (e.g. the C<advancecomp> package under Debian,
956 or the C<advancecomp> port on macports - 7-Zip on Windows is the
957 same code as AdvanceCOMP, so Windows users get the smallest files
958 first time). These compress about 5% smaller than gzip and bzip2.
959 Over the lifetime of your distribution this will save a lot of
960 people a small amount of download time and disk space, which adds
963 In order to produce the C<xz> tarball, XZ Utils are required. The C<xz>
964 utility is included with most modern UNIX-type operating systems and
965 is available for Cygwin. A Windows port is available from
966 L<https://tukaani.org/xz/>.
968 B<IMPORTANT>: if you are on OS X, you must export C<COPYFILE_DISABLE=1>
969 to prevent OS X resource files from being included in your tarball. After
970 creating the tarball following the instructions below, inspect it to ensure
971 you don't have files like F<._foobar>.
973 Create a tarball. Use the C<-s> option to specify a suitable suffix for
974 the tarball and directory name:
976 $ cd root/of/perl/tree
978 $ perl Porting/makerel -x -s RC1 # for a release candidate
979 $ perl Porting/makerel -x # for the release itself
981 This creates the directory F<../perl-x.y.z-RC1> or similar, copies all
982 the MANIFEST files into it, sets the correct permissions on them, then
983 tars it up as F<../perl-x.y.z-RC1.tar.gz>. The C<-x> also produces a
986 If you're getting your tarball suffixed with -uncommitted and you're sure
987 your changes were all committed, you can override the suffix with:
989 $ perl Porting/makerel -x -s ''
991 XXX if we go for extra tags and branches stuff, then add the extra details
994 Finally, clean up the temporary directory, e.g.
996 $ rm -rf ../perl-x.y.z-RC1
998 =head3 test the tarball
1000 Once you have a tarball it's time to test the tarball (not the repository).
1002 =head4 Copy the tarball to a web server
1004 Copy the tarballs (.gz and .xz) to a web server somewhere you have access to.
1006 =head4 Download the tarball to another machine and unpack it
1008 Download the tarball to some other machine. For a release candidate,
1009 you really want to test your tarball on two or more different platforms
1012 =head4 Ask #p5p to test the tarball on different platforms
1014 Once you've verified the tarball can be downloaded and unpacked,
1015 ask the #p5p IRC channel on irc.perl.org for volunteers to test the
1016 tarballs on whatever platforms they can.
1018 If you're not confident in the tarball, you can defer this step until after
1019 your own tarball testing, below.
1021 =head4 Check that F<Configure> works
1023 Check that basic configuration and tests work on each test machine:
1025 $ ./Configure -des && make all minitest test
1027 # Or for a development release:
1028 $ ./Configure -Dusedevel -des && make all minitest test
1030 =head4 Run the test harness and install
1032 Check that the test harness and install work on each test machine:
1035 $ ./Configure -des -Dprefix=/install/path && \
1036 make all test_harness install
1039 (Remember C<-Dusedevel> above, for a development release.)
1041 =head4 Check C<perl -v> and C<perl -V>
1043 Check that the output of C<perl -v> and C<perl -V> are as expected,
1044 especially as regards version numbers, patch and/or RC levels, and @INC
1047 Note that the results may be different without a F<.git/> directory,
1048 which is why you should test from the tarball.
1050 =head4 Run the Installation Verification Procedure utility
1052 $ ./perl -Ilib ./utils/perlivp
1054 $ ./perl5.x.y ./utils/perlivp5.x.y
1056 All tests successful.
1059 =head4 Compare the installed paths to the last release
1061 Compare the pathnames of all installed files with those of the previous
1062 release (i.e. against the last installed tarball on this branch which you
1063 have previously verified using this same procedure). In particular, look
1064 for files in the wrong place, or files no longer included which should be.
1065 For example, suppose the about-to-be-released version is 5.10.1 and the
1068 cd installdir-5.10.0/
1069 find . -type f | perl -pe's/5\.10\.0/5.10.1/g' | sort > /tmp/f1
1070 cd installdir-5.10.1/
1071 find . -type f | sort > /tmp/f2
1074 =head4 Disable C<local::lib> if it's turned on
1076 If you're using C<local::lib>, you should reset your environment before
1077 performing these actions:
1079 $ unset PERL5LIB PERL_MB_OPT PERL_LOCAL_LIB_ROOT PERL_MM_OPT
1081 =head4 Bootstrap the CPAN client
1083 Bootstrap the CPAN client on the clean install:
1090 =head4 Install the Inline module with CPAN and test it
1092 Try installing a popular CPAN module that's reasonably complex and that
1093 has dependencies; for example:
1095 CPAN> install Inline::C
1098 Check that your perl can run this:
1100 $ bin/perl -Ilib -lwe "use Inline C => q[int f() { return 42;}]; print f"
1104 =head4 Make sure that perlbug works
1106 Test L<perlbug> with the following:
1110 Subject: test bug report
1111 Local perl administrator [yourself]:
1117 Action (Send/Display/Edit/Subject/Save to File): f
1118 Name of file to save message in [perlbug.rep]:
1120 and carefully examine the output (in F<perlbug.rep]>), especially
1121 the "Locally applied patches" section.
1123 =for checklist skip BLEAD-POINT
1125 =head3 monitor smokes
1127 XXX This is probably irrelevant if working on a release branch, though
1128 MAINT or RC might want to push a smoke branch and wait.
1130 Wait for the smoke tests to catch up with the commit which this release is
1131 based on (or at least the last commit of any consequence).
1133 Then check that the smoke tests pass (particularly on Win32). If not, go
1134 back and fix things.
1136 Note that for I<BLEAD-POINT> releases this may not be practical. It takes a
1137 long time for the smokers to catch up, especially the Win32
1138 smokers. This is why we have a RC cycle for I<MAINT> and I<BLEAD-FINAL>
1139 releases, but for I<BLEAD-POINT> releases sometimes the best you can do is
1140 to plead with people on IRC to test stuff on their platforms, fire away,
1141 and then hope for the best.
1143 =head3 upload to PAUSE
1145 Once smoking is okay, upload it to PAUSE. This is the point of no return.
1146 If anything goes wrong after this point, you will need to re-prepare
1147 a new release with a new minor version or RC number.
1149 https://pause.perl.org/
1151 (Log in, then select 'Upload a file to CPAN')
1153 If your workstation is not connected to a high-bandwidth,
1154 high-reliability connection to the Internet, you should probably use the
1155 "GET URL" feature (rather than "HTTP UPLOAD") to have PAUSE retrieve the
1156 new release from wherever you put it for testers to find it. This will
1157 eliminate anxious gnashing of teeth while you wait to see if your
1158 15 megabyte HTTP upload successfully completes across your slow, twitchy
1161 I<Remember>: if your upload is partially successful, you
1162 may need to contact a PAUSE administrator or even bump the version of perl.
1164 Upload the .gz and .xz versions of the tarball.
1166 Note: You can also use the command-line utility to upload your tarballs, if
1167 you have it configured:
1169 cpan-upload perl-5.X.Y.tar.gz
1170 cpan-upload perl-5.X.Y.tar.xz
1172 Do not proceed any further until you are sure that your tarballs are on CPAN.
1173 Check your authors directory metacpan.org to confirm that your uploads have
1176 https://metacpan.org/author/YOUR_PAUSE_ID
1178 =for checklist skip RC BLEAD-POINT
1180 =head3 wait for indexing
1182 I<You MUST SKIP this step for RC and BLEAD-POINT>
1184 Wait until you receive notification emails from the PAUSE indexer
1185 confirming that your uploads have been received. IMPORTANT -- you will
1186 probably get an email that indexing has failed, due to module permissions.
1187 This is considered normal.
1189 =for checklist skip BLEAD-POINT
1191 =head3 disarm patchlevel.h
1193 I<You MUST SKIP this step for BLEAD-POINT release>
1195 Disarm the F<patchlevel.h> change; for example,
1197 static const char * const local_patches[] = {
1200 #ifdef PERL_GIT_UNCOMMITTED_CHANGES
1201 ,"uncommitted-changes"
1204 Be sure to commit your change:
1206 $ git commit -m 'Disarm RCnnn bump' patchlevel.h
1208 =head3 announce to p5p
1210 Mail perl5-porters@perl.org to announce your new release, with a quote you prepared earlier.
1211 Get the SHA256 digests from the PAUSE email responses.
1213 Use the template at Porting/release_announcement_template.txt
1215 Send a carbon copy to C<noc@metacpan.org>
1217 If your email does not appear on the list, but does not obviously bounce
1218 either, check that the email you are sending from is subscribed to the list.
1220 =head3 merge release branch back to blead
1222 Merge the (local) release branch back into master now, and delete it.
1226 git merge release-5.xx.yy
1228 git branch -d release-5.xx.yy
1230 Note: The merge will create a merge commit if other changes have been pushed
1231 to blead while you've been working on your release branch. Do NOT rebase your
1232 branch to avoid the merge commit (as you might normally do when merging a
1233 small branch into blead) since doing so will invalidate the tag that you
1236 =head3 publish the release tag
1238 Now that you've shipped the new perl release to PAUSE and pushed your changes
1239 to the Perl master repository, it's time to publish the tag you created
1242 $ git push origin tag v5.11.0
1244 =head3 update epigraphs.pod
1246 Add your quote to F<Porting/epigraphs.pod> and commit it.
1247 You can include the customary link to the release announcement even before your
1248 message reaches the web-visible archives by looking for the X-List-Archive
1249 header in your message after receiving it back via perl5-porters.
1251 =head3 blog about your epigraph
1253 If you have a blog, please consider writing an entry in your blog explaining
1254 why you chose that particular quote for your epigraph.
1256 =head3 update the link to the latest perl on perlweb
1258 Submit a pull request to L<https://github.com/perlorg/perlweb>. For a dev
1259 release, update the link in F<docs/dev/perl5/index.html>. For a stable
1260 release, update F<docs/shared/tpl/stats.html>.
1262 =for checklist skip RC
1264 =head3 Release schedule
1266 I<You MUST SKIP this step for RC>
1268 Tick the entry for your release in F<Porting/release_schedule.pod>.
1270 =for checklist skip RC
1272 =head3 Module::CoreList nagging
1274 I<You MUST SKIP this step for RC>
1276 Remind the current maintainer of C<Module::CoreList> to push a new release
1279 =for checklist skip RC
1281 =head3 new perldelta
1283 I<You MUST SKIP this step for RC>
1285 Create a new perldelta.
1291 Confirm that you have a clean checkout with no local changes.
1296 perl Porting/new-perldelta.pl
1300 Run the C<git add> commands it outputs to add new and modified files.
1304 Verify that the build still works, by running C<./Configure> and
1305 C<make test_porting>. (On Win32 use the appropriate make utility).
1309 If F<t/porting/podcheck.t> spots errors in the new F<pod/perldelta.pod>,
1310 run C<./perl -MTestInit t/porting/podcheck.t | less> for more detail.
1311 Skip to the end of its test output to see the options it offers you.
1315 When C<make test_porting> passes, commit the new perldelta.
1317 git commit -m'New perldelta for 5.X.Y'
1321 At this point you may want to compare the commit with a previous bump to
1322 see if they look similar. See commit ba03bc34a4 for an example of a
1323 previous version bump.
1325 =for checklist skip MAINT RC
1329 I<You MUST SKIP this step for RC and MAINT>
1331 If this was a BLEAD-FINAL release (i.e. the first release of a new maint
1332 series, 5.x.0 where x is even), then bump the version in the blead branch
1333 in git, e.g. 5.12.0 to 5.13.0.
1335 First, add a new feature bundle to F<regen/feature.pl>, initially by just
1336 copying the exiting entry, and bump the file's $VERSION (after the __END__
1339 "5.14" => [qw(switch say state unicode_strings)],
1340 + "5.15" => [qw(switch say state unicode_strings)],
1342 Run F<regen/feature.pl> to propagate the changes to F<lib/feature.pm>.
1344 Then follow the section L<"Bump the version number"> to bump the version
1345 in the remaining files and test and commit.
1347 If this was a BLEAD-POINT release, then just follow the section
1348 L<"Bump the version number">.
1350 After bumping the version, follow the section L<"update INSTALL"> to
1351 ensure all version number references are correct.
1353 (Note: The version is NOT bumped immediately after a MAINT release in order
1354 to avoid confusion and wasted time arising from bug reports relating to
1355 "intermediate versions" such as 5.20.1-and-a-bit: If the report is caused
1356 by a bug that gets fixed in 5.20.2 and this intermediate version already
1357 calls itself 5.20.2 then much time can be wasted in figuring out why there
1358 is a failure from something that "should have been fixed". If the bump is
1359 late then there is a much smaller window of time for such confusing bug
1360 reports to arise. (The opposite problem -- trying to figure out why there
1361 *is* a bug in something calling itself 5.20.1 when in fact the bug was
1362 introduced later -- shouldn't arise for MAINT releases since they should,
1363 in theory, only contain bug fixes but never regressions.))
1365 =head3 clean build and test
1367 Run a clean build and test to make sure nothing obvious is broken. This is
1368 very important, as commands run after this point must be run using the perl
1369 executable built with the bumped version number.
1372 $ ./Configure -des -Dusedevel
1376 In particular, F<Porting/perldelta_template.pod> is intentionally exempted
1377 from podchecker tests, to avoid false positives about placeholder text.
1378 However, once it's copied to F<pod/perldelta.pod> the contents can now
1379 cause test failures. Problems should be resolved by doing one of the
1386 Replace placeholder text with correct text.
1390 If the problem is from a broken placeholder link, you can add it to the
1391 array C<@perldelta_ignore_links> in F<t/porting/podcheck.t>. Lines
1392 containing such links should be marked with C<XXX> so that they get
1393 cleaned up before the next release.
1397 Following the instructions output by F<t/porting/podcheck.t> on how to
1398 update its exceptions database.
1404 Finally, push any commits done above.
1406 $ git push origin ....
1408 =for checklist skip BLEAD-POINT MAINT RC
1410 =head3 create maint branch
1412 I<You MUST SKIP this step for RC, BLEAD-POINT, MAINT>
1414 If this was a BLEAD-FINAL release (i.e. the first release of a new maint
1415 series, 5.x.0 where x is even), then create a new maint branch based on
1416 the commit tagged as the current release.
1418 Assuming you're using git 1.7.x or newer:
1420 $ git checkout -b maint-5.12 v5.12.0
1421 $ git push origin -u maint-5.12
1424 =for checklist skip BLEAD-POINT MAINT RC
1426 =head3 make the maint branch available in the APC
1428 Clone the new branch into /srv/gitcommon/branches on camel so the APC will
1429 receive its changes.
1431 $ git clone --branch maint-5.14 /gitroot/perl.git \
1432 ? /srv/gitcommon/branches/perl-5.14.x
1433 $ chmod -R g=u /srv/gitcommon/branches/perl-5.14.x
1435 And nag the sysadmins to make this directory available via rsync.
1437 XXX Who are the sysadmins? Contact info?
1439 =for checklist skip BLEAD-POINT RC
1441 =head3 copy perldelta.pod to blead
1443 I<You MUST SKIP this step for RC, BLEAD-POINT>
1445 Copy the perldelta.pod for this release into blead; for example:
1448 $ cp -i ../5.10.x/pod/perldelta.pod pod/perl5101delta.pod #for example
1449 $ git add pod/perl5101delta.pod
1451 Don't forget to set the NAME correctly in the new file (e.g. perl5101delta
1452 rather than perldelta).
1454 Edit F<pod/perl.pod> to add an entry for the file, e.g.:
1456 perl5101delta Perl changes in version 5.10.1
1458 Then rebuild various files:
1460 $ perl Porting/pod_rules.pl
1462 Finally, commit and push:
1464 $ git commit -a -m 'Add perlXXXdelta'
1465 $ git push origin ....
1467 =for checklist skip BLEAD-POINT
1469 =head3 copy perlhist.pod entries to blead
1471 Make sure any recent F<pod/perlhist.pod> entries are copied to
1472 F<perlhist.pod> on blead. e.g.
1478 I<You MUST RETIRE to your preferred PUB, CAFE or SEASIDE VILLA for some
1479 much-needed rest and relaxation>.
1481 Thanks for releasing perl!
1483 =head2 Building a release - the day after
1485 =for checklist skip BLEAD-FINAL MAINT RC
1487 =head3 update Module::CoreList
1489 I<After a BLEAD-POINT release only>
1491 After Module::CoreList has shipped to CPAN by the maintainer, update
1492 Module::CoreList in the source so that it reflects the new blead
1499 Update F<Porting/Maintainers.pl> to list the new DISTRIBUTION on CPAN,
1500 which should be identical to what is currently in blead.
1504 Bump the $VERSION in F<dist/Module-CoreList/lib/Module/CoreList.pm>
1505 and F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm>.
1509 If you have a local CPAN mirror, run:
1511 $ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror
1515 $ ./perl -Ilib Porting/corelist.pl cpan
1517 This will update F<dist/Module-CoreList/lib/Module/CoreList.pm> and
1518 F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm> as it did before,
1519 but this time adding new sections for the next BLEAD-POINT release.
1523 Add the new $Module::CoreList::VERSION to
1524 F<dist/Module-CoreList/Changes>.
1528 Remake perl to get your changed .pm files propagated into F<lib/> and
1529 then run at least the F<dist/Module-CoreList/t/*.t> tests and the
1530 test_porting makefile target to check that they're ok.
1532 $ cd t; ./TEST ../dist/Module-CoreList/t/*.t
1539 $ ./perl -Ilib -MModule::CoreList \
1540 -le 'print Module::CoreList->find_version($]) ? "ok" : "not ok"'
1542 and check that it outputs "ok" to prove that Module::CoreList now knows
1543 about blead's current version.
1547 Commit and push your changes.
1550 $ git commit -m "Prepare Module::Corelist for 5.XX.Y"
1555 =head3 check tarball availability
1557 Check various website entries to make sure the that tarball has appeared
1558 and is properly indexed:
1564 Check your author directory under L<https://www.cpan.org/authors/id/>
1565 to ensure that the tarballs are available on the website.
1569 Check F</src> on CPAN (on a fast mirror) to ensure that links to
1570 the new tarballs have appeared: There should be links in F</src/5.0>
1571 (which is accumulating all new versions), and (for BLEAD-FINAL and
1572 MAINT only) an appropriate mention in F</src/README.html> (which describes
1573 the latest versions in each stable branch, with links).
1575 The F</src/5.0> links should appear automatically, some hours after upload.
1576 If they don't, or the F</src> description is inadequate,
1577 ask Ask <ask@perl.org>.
1581 Check L<https://www.cpan.org/src/> to ensure that the F</src> updates
1582 have been correctly mirrored to the website.
1583 If they haven't, ask Ask <ask@perl.org>.
1587 Check L<https://metacpan.org> to see if it has indexed the distribution.
1588 It should be visible at a URL like C<https://metacpan.org/release/DAPM/perl-5.10.1>.
1592 =head3 update release manager's guide
1594 Go over your notes from the release (you did take some, right?) and update
1595 F<Porting/release_managers_guide.pod> with any fixes or information that
1596 will make life easier for the next release manager.
1603 L<http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2009-05/msg00608.html>,
1604 plus a whole bunch of other sources, including private correspondence.