view release on metacpan or  search on metacpan

RELEASE  view on Meta::CPAN

Instructions for Apache-Dispatch Release Manager

1. 'make dist' - to make sure nothing is missing from the manifest,
   etc. Now test this generated package (not svn) with as many
   configurations as possible on as many platforms as possible.

  a. edit ./Changes:
     - find lib -type f -name "*.pm" | \
         xargs perl -pi -e 's,0.12-dev,0.12-RC1,g'
     - perl -pi -e 's,0.12-dev,0.12-RC1,g' Changes

     - don't commit these (see dev@ archives)

  b. nuke any preinstalled Apache-Dispatch libs and run 'make test'

  c. test that you can 'make install' and then run 'make test' again

RELEASE  view on Meta::CPAN

  Subject: [RELEASE CANDIDATE] Apache-Dispatch 0.12 RC\d+

   (or maybe longer to give most people a chance to catch up). no need
   to tag this package

  a. if problems are detected during stage 2, repeat stages 1 and 2.

3. when the package has been reported to be good, prepare a new
   package to be released

  a. edit ./Changes:
     - remove -RC\d+
     - add release date

  b. rerun:
     % perl Makefile.PL
     make sure tag looks right
     % make -n tag

  c. commit Changes
     % svn ci Changes

RELEASE  view on Meta::CPAN

  a. post ... to the modperl, announce lists
  Subject: [ANNOUNCE] Apache-Dispatch 0.12
     include 
  - MD5 sig (as it comes from CPAN upload announce).
  - the latest Changes

6. Prepare for the next cycle

  a. increment version in lib/Apache/Dispatch.pm

  b. edit ./Changes:
     - start a new item with incremented version + '-dev'

  =item 0.12-dev

  c. bump up version numbers in this file to make it easier to do the
     next release.

     $ perl -pi -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE

  d. commit Changes