view release on metacpan or  search on metacpan

HOWTO.release  view on Meta::CPAN

Steps for creating new releases
===============================

 * Bump version in lib/App/KGB.pm
 * Update Changes and debian/changelog (git-dch)
 * `make distcheck`, update MANIFEST{,SKIP} as needed.
 * `make dist'
 * build/upload for Debian
   + make orig to get a .orig.tar file in ../
 * upload to CPAN
   + cpan-upload -u USERID ../App-KGB-*.tar.gz

TODO  view on Meta::CPAN

  "406 Not Acceptable"

* admin/sync -- needs a plan
  Plan A
  ======
  - we need a system which would allow individual instances' admins to update
    some central configuration store, which is both encrypted and signed.
  - that central store could be fetched by the bots regularly, the signature
    verified, and then the changes applied.
  - the central storage could be on alioth, but the signing should be done
    remotely somehow (who wants to upload her secret hey to alioth? :))
    there could be a tool that automates the signing process (download from
    alioth, start $EDITOR or add config from command line, sign, upload)
  - the bots need to be given a keyring with trusted keys, whose signatures
    they recognise

  Pros:
   - powerful
   - possible addition/modification and removal of project
   - full encryption end-to-end
  Cons:
   - GPG integration in the bot
   - complex configuraion retrieval