Choose Your Own Tutorial
Releasing Your Distribution
If you release your code to the CPAN, you probably want these three plugin in your configuration:
1: | [TestRelease] |
With those plugins in place, the dzil release command will:
write a tarball to disk
ensure that it can be extracted and successfully tested
prompt you for one last confirmation
upload the distribution to PAUSE (the Perl author upload server)
To let Dist::Zilla upload on your behalf, you'll want a ~/.pause file with contents like this:
user RJBS
password PeasAreDeliciousEverything else will just work!
Trial Releases
Normally, when you run dzil release, the distribution uploaded to the CPAN is ready for indexing. That means that it becomes the current, stable, indexed source of all the packages it contains. If someone tries to install Your::Library, they'll start getting the one from the release you just made.
Sometimes, you want to upload a dist to the CPAN that can be found and downloaded by interested people (or by automated testers running against the bleading edge). The solution is to make a trial release. This release will look just like any other release, but it won't be indexed by PAUSE, so it won't be automatically chosen as the latest available version by CPAN clients.
To make a trial release, just run:
$ dzil release --trialIf you'd like to learn about how Dist::Zilla builds your dist, turn to page 14
If you'd like to learn how to run your dist's tests, turn to page 8
If you'd like to learn how to integrate the release process with your VCS, turn to page 10
If you'd like to learn about managing version numbers with Dist::Zilla, turn to page 6