My checklist for the developer release 5.25.10 of the programming language Perl.
Make sure you have a PAUSE account suitable for uploading a perl release. If you don't have a PAUSE account, then request one:
Check that your account is allowed to upload perl distros: go to https://pause.perl.org/pause/authenquery?ACTION=who_pumpkin and check that your PAUSE ID is listed there. If not, ask Andreas König to add your ID to the list of people allowed to upload something called perl. You can find Andreas' email address at:
Make sure you have permission to close tickets on http://rt.perl.org/ so you can respond to bug report as necessary during your stint. If you don't, make an account (if you don't have one) and contact the pumpking with your username to get ticket-closing permission.
You will need a working git installation, checkout of the perl git repository and perl commit bit. For information about working with perl and git, see pod/perlgit.pod.
If you are not yet a perl committer, you won't be able to make a release. Have a chat with whichever evil perl porter tried to talk you into the idea in the first place to figure out the best way to resolve the issue.
You will need to be able to share tarballs with #p5p members for pre-release testing, and you may wish to upload to PAUSE via URL. Make sure you have a way of sharing files, such as a web server or file-sharing service.
Porters have access to the "dromedary" server (users.perl5.git.perl.org), which has a public_html directory to share files with. (http://users.perl5.git.perl.org/~username/perl-5.xx.y.tar.gz)
If you use Dropbox, you can append "raw=1" as a parameter to their usual sharing link to allow direct download (albeit with redirects).
For updating the http://dev.perl.org web pages, either a Github account or sweet-talking somebody with a Github account into obedience is needed. This 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.
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.
When the tarball is created, you should check it (preferrably on more than one machine.