Eric Wilhelm wrote:
> # 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
List all tags:
git tag -l
Get the latest tag:
git describe --abbrev=0 --tags
Show all changes from a $tag to now:
git log $tag..HEAD
> (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
svn up git pull
svn st git status (returns non-zero if nothing to commit)
Check that you're on the master branch:
`git describe --all` eq "heads/master\n"
> 2. create a tag
svn cp repo/trunk repo/tags/$tag git tag $tag -m 'Optional message'
> (and all of this needs to be atomically/cleanly sync'd to the "global"
> repository before sending a tarball to the CPAN)
git push origin
> 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.
Where's the release script? I see devtools/release_instructions.pod but no
script.
--
191. Our Humvees cannot be assembled into a giant battle-robot.
-- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
http://skippyslist.com/list/
