pkgsrc/devel/p5-ShipIt/distinfo

$NetBSD: distinfo,v 1.2 2010/03/16 23:05:01 sno Exp $

SHA1 (ShipIt-0.53.tar.gz) = 21d6e66e24aad660fb84e8ab6b3c7f274904169a
RMD160 (ShipIt-0.53.tar.gz) = 01e34adb0b2190eb5ce0bd3187d8ca797d3de551
Size (ShipIt-0.53.tar.gz) = 16748 bytes
Updating devel/p5-ShipIt from 0.52 to 0.53 pkgsrc changes: - Add license definition Upstream changes: 0.53 (2009-12-15) * Mercurial support * Module::Build support 2010-03-17 00:05:01 +01:00			$NetBSD: distinfo,v 1.2 2010/03/16 23:05:01 sno Exp $
Initial import of p5-ShipIt version 0.52 in 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. 2008-10-22 20:40:54 +02:00
Updating devel/p5-ShipIt from 0.52 to 0.53 pkgsrc changes: - Add license definition Upstream changes: 0.53 (2009-12-15) * Mercurial support * Module::Build support 2010-03-17 00:05:01 +01:00			`SHA1 (ShipIt-0.53.tar.gz) = 21d6e66e24aad660fb84e8ab6b3c7f274904169a`
			`RMD160 (ShipIt-0.53.tar.gz) = 01e34adb0b2190eb5ce0bd3187d8ca797d3de551`
			`Size (ShipIt-0.53.tar.gz) = 16748 bytes`