Maxima version and git describe and git workflow

On 02/25/2013 10:14 AM, Raymond Toy wrote:
> In a recent message it was noted that the maxima version on the
> current master branch is something like 5.28.0_314.  This version
> comes from git describe which derives the version from the "closest"
> annotated tag.
>
> Since we've released 5.29.x, it would make more sense if the version
> were something like 5.29_nnn.
>
> I'm not really familiar with the git workflow, but I think that for
> each release that is done, we should probably create (an annotated)
> tag it.  (I couldn't find any 5.29 tag.)  We might also have to merge
> that tagged version back to master to keep things consistent.
>
> I think if we did that git describe will produce the correct version
> on the master branch as well.
>
> Does this make sense?
>
> Ray
>
>
> _______________________________________________
> Maxima mailing list
> Maxima at math.utexas.edu
> http://www.math.utexas.edu/mailman/listinfo/maxima
>
Hello Ray:

I think I agree with what you say, but I'm pretty much a git novice so I 
don't know for sure.
If having that tag would make it so the default git download would build 
the latest version of Maxima without having to do an additional checkout 
step to get the latest code, then that would be ideal from my 
perspective. I only use git occasionally to download software source 
packages to build and I don't have a deep understanding of its inner 
workings.

Respectfully,

Paul Bowyer