[pkgsrc/trunk]: pkgsrc/doc Note initial addition of p5-ShipIt version 0.52 as...

[seb <seb%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/1cdcd55afea8
branches:  trunk
changeset: 548754:1cdcd55afea8
user:      seb <seb%pkgsrc.org@localhost>
date:      Wed Oct 22 18:43:53 2008 +0000

description:
Note initial addition of p5-ShipIt version 0.52 as devel/p5-ShipIt
into The NetBSD Packages Collection.

Releasing a new version of software (Perl module) takes a lot of
steps... finding the next version number (and making sure you didn't
already use that version number before), making sure your changelog
is updated, making sure your "make dist" results in a tarball that
builds, commiting changes (with updated version number), tagging,
and uploading the tarball somewhere.  Or maybe more steps. Or not
some of the above. Maybe you forgot something! And maybe you manage
multiple projects, and each project has a different release process.
You want to be hacking, not jumping through hoops.  Your contributors
want to see their patches actually make it into a release, which
won't happen if you're afraid of releases.  shipit automates all
the hell. It makes life beautiful.

diffstat:

 doc/CHANGES-2008 |  3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diffs (14 lines):

diff -r 61358c817a25 -r 1cdcd55afea8 doc/CHANGES-2008
--- a/doc/CHANGES-2008  Wed Oct 22 18:42:42 2008 +0000
+++ b/doc/CHANGES-2008  Wed Oct 22 18:43:53 2008 +0000
@@ -1,4 +1,4 @@
-$NetBSD: CHANGES-2008,v 1.2584 2008/10/22 16:35:59 tonnerre Exp $
+$NetBSD: CHANGES-2008,v 1.2585 2008/10/22 18:43:53 seb Exp $
 
 Changes to the packages collection and infrastructure in 2008:
 
@@ -4468,3 +4468,4 @@
        Added chat/ruby-net-irc version 0.0.5 [obache 2008-10-22]
        Updated x11/ruby-gnome2-gtk to 0.18.0nb1 [obache 2008-10-22]
        Added security/py-asn1 version 0.0.8a [tonnerre 2008-10-22]
+       Added devel/p5-ShipIt version 0.52 [seb 2008-10-22]