view release on metacpan or  search on metacpan

build/RELEASE  view on Meta::CPAN

   current directory.   You should keep this source tree
   intact to tag the final release.


5. Test the generated file with

        % make release_test

   Make sure all perl tests pass.

6. Sign it via gpg:

        % gpg --detach-sign --armor libapreq2-2.16.tar.gz

   or pgp:

        % pgp -sba libapreq2-2.16.tar.gz

7. Upload the release candidate to people.apache.org/~username
   and post a candidate announcement to apreq-dev@. Also, it is 
   strongly recommended that the RM crosspost the candidate 
   announcement to the modperl@ list, to solicit feedback
   from a much larger audience.

build/RELEASE  view on Meta::CPAN

10. Upload (scp) the package, signature and MD5/SHA* hash files to
   www.apache.org for distribution:
   
        $ svn co https://dist.apache.org/repos/dist/release/httpd/libapreq/ apreq-dist-site
        $ cp libapreq2-2.16.tar.gz* apreq-dist-site
        $ svn commit -m "libapreq2 2.16 release artifacts"

   Ask another developer to confirm the uploaded signature is ok.

        % gpg --verify libapreq2-2.16.tar.gz.asc
        % pgp libapreq2-2.16.tar.gz.asc

   Check that your public key is among those listed in the
   /www/www.apache.org/dist/httpd/KEYS file.   If not, you
   need to commit the necessary change to KEYS the httpd-dist repos.
   Then update the website's copy using "cvs co KEYS" in the 
   /www/www.apache.org/dist/httpd/ directory.

11. Verify or get soeone to Verify that you have CPAN karma.
    Note, discuss getting a group kind of like AMPL in mod_perl land.