Release procedure

The procedure for creating a source distribution for a new release of Daizu.

Follow these instructions if you're releasing a new version of the Daizu CMS source package.

  1. Update the version number:
    • $VERSION in lib/Daizu.pm
    • version in META.yml (the top-level one, not the one in meta-spec)

  2. Update the Changes file with a new section for a matching version number, with the date the release will be published and the revision number in which its tag will be created.

  3. Add any new upgrade scripts to the no_index part of META.yml so that CPAN won't try to index them.

  4. ./Build realclean

  5. Run chkmanifest.pl and make sure there's nothing you want to distribute missing.

  6. Run mkbuild.pl and make sure that the tests run all the way through without any unexpected problems.

  7. Make sure everything is committed, and copy the trunk to a tag like tags/release/1.2.3

  8. Make the distribution tarball, take it to another machine, and build and test there.

  9. Add the new tarball to the website and update the downloads page, and if appropriate the roadmap page. At the same time write a blog article providing the release notes.

  10. Upload the tarball to CPAN