Version 4 (modified by Dominic Hargreaves, 15 years ago) (diff)


This is the process the release manager goes through to release

  1. Call a feature freeze on the mailing list
  2. See if the test suite passes. If not, find, fix and commit.
  3. Take a diff from the previous release eg:
    svn diff
    and put it into a temp file.
  4. Work through the diff with an editor, deleting as you go and chasing up any changes that don't make sense or need adjustment. The idea is that you end up with an empty file when you've reviewed it all.
  5. During the above process you will probably have found bugs, and fixed them. Commit that.
  6. See if the test suite passes. If not, find, fix and commit.
  7. Check that the following files are up-to-date:
    • Changes
    • MANIFEST (file lists)
    • Build.PL (file lists and module dependencies)
    • PREREQUISITES (module dependencies)
  8. Update any year numbers in the copyright notices if the year has changed and the file has been updated
  9. Update the version number in wiki.cgi and lib/
  10. If any other .pm files have updated, update version numbers there too.
  11. Make an internal release candidate:
    perl Build.PL
    perl Build dist
  12. From that release candidate, test a new install and an upgrade
  13. Do some user testing on that install; fix any bugs encountered
  14. See if the test suite passes. If not, find, fix and commit.
  15. Add a date to the version in Changes
  16. Tag the release
    [from trunk/]
    svn copy .
  17. Run utils/build-tarball-from-svn-tag to make the tarball
  18. Upload tarball to personal web space
  19. Go to to upload the tarball to CPAN via the above web space
  20. Build and upload Debian packages (note: you will probably need to sync the supplied wiki.conf!)
  21. Send message to the mailing list
  22. Wait for a while to let CPAN update and Debian mirror sync happen, then add release to Freshmeat.