---
- branch: MAIN
  date: Wed Oct 22 18:40:54 UTC 2008
  files:
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-ShipIt/DESCR
    pathrev: pkgsrc/devel/p5-ShipIt/DESCR@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-ShipIt/distinfo
    pathrev: pkgsrc/devel/p5-ShipIt/distinfo@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-ShipIt/Makefile
    pathrev: pkgsrc/devel/p5-ShipIt/Makefile@1.1.1.1
    type: imported
  id: 20081022T184054Z.b528ea9ef1aed0c874c1f13fe69e835eddabf491
  log: "Initial import of p5-ShipIt version 0.52 in the NetBSD Packages\nCollection.\n\nReleasing
    a new version of software (Perl module) takes a lot of\nsteps... finding the next
    version number (and making sure you didn't\nalready use that version number before),
    making sure your changelog\nis updated, making sure your \"make dist\" results
    in a tarball that\nbuilds, commiting changes (with updated version number), tagging,\nand
    uploading the tarball somewhere.  Or maybe more steps. Or not\nsome of the above.
    Maybe you forgot something! And maybe you manage\nmultiple projects, and each
    project has a different release process.\nYou want to be hacking, not jumping
    through hoops.  Your contributors\nwant to see their patches actually make it
    into a release, which\nwon't happen if you're afraid of releases.  shipit automates
    all\nthe hell. It makes life beautiful.\n\nStatus:\n\nVendor Tag:\tTNF\nRelease
    Tags:\tpkgsrc-base\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/p5-ShipIt'
  unixtime: '1224700854'
  user: seb