My checklist for the developer release 5.25.10 of the programming language Perl.
After a BLEAD-POINT release only
After Module::CoreList has shipped to CPAN by the maintainer, update Module::CoreList in the source so that it reflects the new blead version number:
$ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror
$ ./perl -Ilib Porting/corelist.pl cpan
This will update dist/Module-CoreList/lib/Module/CoreList.pm and dist/Module-CoreList/lib/Module/CoreList/Utils.pm as it did before, but this time adding new sections for the next BLEAD-POINT release.
$ ./perl -Ilib -MModule::CoreList \ -le 'print Module::CoreList->find_version($]) ? "ok" : "not ok"'
and check that it outputs "ok" to prove that Module::CoreList now knows about blead's current version.
Check various website entries to make sure the that tarball has appeared and is properly indexed:
The /src/5.0 links should appear automatically, some hours after upload. If they don't, or the /src description is inadequate, ask Ask <firstname.lastname@example.org>.
You MUST SKIP this step for a RC release
perlweb repository, link to the new release. For a new latest-maint release, edit docs/shared/tpl/stats.html. Otherwise, edit docs/dev/perl5/index.html.
Then make a pull request to Leo Lapworth. If this fails for some reason and you cannot cajole anybody else into submitting that change, you can mail Leo as last resort.
This repository can be found on github.
Go over your notes from the release (you did take some, right?) and update Porting/release_managers_guide.pod with any fixes or information that will make life easier for the next release manager.