# from Michael G Schwern
# on Saturday 13 June 2009 21:33:
>+MAX_INT
>
>I can do it, I've done it often enough and I think the MB repo is
> pretty simple
My concern is still for the release process. I need to be able to
easily pull a sequential log of commit messages since the last release
tag (to check/update the Changes file) and the release tool needs to
know how to:
1. verify that the working directory is current *and* committed
2. create a tag
(and all of this needs to be atomically/cleanly sync'd to the "global"
repository before sending a tarball to the CPAN)
I'm sure that's all "no problem" with git, but it is some non-zero
amount of work for me to update the process (vs zero amount of work for
me if it doesn't change.) We want to keep releases *easy*, so please
include the above in any transition effort/plan.
Thanks,
Eric
--
Turns out the optimal technique is to put it in reverse and gun it.
--Steven Squyres (on challenges in interplanetary robot navigation)
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
