I spent some time looking into this issue last week. It turns out that
git has a command (git describe) that will provide a useful version
number for nightly releases, based on the last tag name, number or
revisions since then, and a substring of the hash of the commit.

Version numbers would look like: 0.7-145-fe521c92

This would be the 145th commit after the tag for 0.7, with a hash that
is useful for finding the commit tree.

We can incorporate this into our build process, but it won't work
until we use git to tag a new release. Because all of our current tags
were created in svn, git can't seem to see them to be used in git
describe.

Soon!

Owen

-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev

Reply via email to