Releasing a new version of software 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. This is all a pain in the ass. 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. WWW: http://search.cpan.org/dist/ShipIt/ Generated with FreeBSD Port Tools 0.77
Responsible Changed From-To: freebsd-ports-bugs->clsung clsung@ wants his PRs
clsung 2007-05-29 02:46:53 UTC FreeBSD ports repository Modified files: devel Makefile Added files: devel/p5-ShipIt Makefile distinfo pkg-descr pkg-plist Log: Add p5-ShipIt 0.50, software release tool. PR: ports/112376 Submitted by: Gea-Suan Lin <gslin at gslin.org> Revision Changes Path 1.2767 +1 -0 ports/devel/Makefile 1.1 +25 -0 ports/devel/p5-ShipIt/Makefile (new) 1.1 +3 -0 ports/devel/p5-ShipIt/distinfo (new) 1.1 +21 -0 ports/devel/p5-ShipIt/pkg-descr (new) 1.1 +31 -0 ports/devel/p5-ShipIt/pkg-plist (new) _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: open->closed New port added. Thank You.