On Sat, Aug 10, 2013 at 10:21 AM, Merlijn van Deen <valhallasw(a)arctus.nl>wrote;wrote:
Hi xqt and dr. trigon,
On 1 August 2013 13:33, <info(a)gno.de> wrote:
Hi folks,
unfortunately the git Id numer is not a sequential release number as in
svn but a hash. I find it a good idea to have a release number in the code
as it was before git migration. A git statement generates it:
git rev-list HEAD | wc -l
which is the revision number. A better idea would be the gerrit number
which gives us the last and actual change for that code. It is posible to
merge such a number to the __version__ header of the script instead or in
addition to the hash?
Although this is possible, I'm not sure what we gain by doing this - is
the problem the length of the hash? Or do you want a number that increases?
If so - why?
I see it can be useful to quickly determine how old someone's version is,
but we can add logic to version.py to do that (e.g. including date). In my
experience, it was never very useful to see who touched a file for the last
time - and it's quickly available using git log <filename> (although this
might be harder on windows?)
I'd suggest using semantic version numbers (
http://semver.org/) for
git annotated tags (make sure to push them to the server too) and then use
`git describe` as a reasonable approximation of the SVN revision number,
but with more information provided as to the significance of changes than a
simple revision counter.
Tom