mod_perl

 view release on metacpan or  search on metacpan

Apache-SizeLimit/RELEASE  view on Meta::CPAN

   on dev@perl.

   make sure your public key is in the KEYS file in the mod_perl docs.
   you should only need to do this if this is your first time playing
   Release Manager

     $ cd mod_perl-docs
     $ grep $USER src/dist/KEYS

   note that the KEYS file itself contains all the instructions you
   need on how to add your key.  if you need further help on gpg
   (like how to create a key in the first place) you can look here

      http://people.apache.org/~geoff/gpghowto.html

   Copy the KEYS file into place:
   % scp KEYS www.apache.org:/www/www.apache.org/dist/perl/KEYS

   If this is your first release, ask someone with APML karma on PAUSE
   to verify you have the appropriate permissions.  Likely someone on
   the PMC can do this.

  a. login into https://pause.perl.org
  b. menu click: Select Mailinglist/Action

RELEASE  view on Meta::CPAN

Instructions for mod_perl 2.0 Release Manager

0. make sure your public key is in the KEYS file in the mod_perl docs.
   you should only need to do this if this is your first time playing
   Release Manager

     $ cd mod_perl-docs
     $ grep $USER src/dist/KEYS

   note that the KEYS file itself contains all the instructions you
   need on how to add your key.  if you need further help on gpg
   (like how to create a key in the first place) you can look here

      https://people.apache.org/~geoff/gpghowto.html

   Copy the KEYS file into place:
   % scp KEYS people.apache.org:/www/www.apache.org/dist/perl/KEYS

   If this is your first release, ask someone with APML karma on PAUSE 
   to verify you have the appropriate permissions.  Likely someone on 
   the PMC can do this.

  a. login into https://pause.perl.org
  b. menu click: Select Mailinglist/Action

RELEASE  view on Meta::CPAN

  h. test the final package again at least once

4. Tarball signing

   (depending on whether you use GPG or PGP, pick the first or the
   second set of the commands):

  a. sign your local copy of the tarball:

     % gpg --detach-sign --armor mod_perl-2.0.13.tar.gz

     % pgps -b --armor mod_perl-2.0.13.tar.gz

  b. create SHA256 and SHA512 checksums of the tarball:
     % sha256sum mod_perl-2.0.13.tar.gz >mod_perl-2.0.13.tar.gz.sha256
     % sha512sum mod_perl-2.0.13.tar.gz >mod_perl-2.0.13.tar.gz.sha512

5. Release the package and update links

  a. commit the tarball, the signature file and the checksum files to

RELEASE  view on Meta::CPAN

     already have been archived at https://archive.apache.org/dist/perl/)

  c. update the example command-lines in README.html in the same location

  d. ask one of the other developers to double check the signature file
     and tarball: download both files and verify the signature:

     https://www.apache.org/dist/perl/mod_perl-2.0.13.tar.gz.asc
     https://www.apache.org/dist/perl/mod_perl-2.0.13.tar.gz

     % gpg --verify mod_perl-2.0.13.tar.gz.asc

     % pgpv mod_perl-2.0.13.tar.gz.asc

  e. respond to the automated email that will arrive requesting that release
     data be filled in at https://reporter.apache.org/addrelease.html?perl

  f. update the version and release date in the docs:
     % vi modperl-docs/src/download/index_top.html 
     % vi modperl-docs/doap_Perl.rdf
     and commit.