git version tags

[Jannis Pohlmann]

Hey,

On Tue, 28 Jul 2009 16:11:22 -0700
"Brian J. Tarricone" <brian at tarricone.org> wrote:

> But I guess the problem boils down to two questions:
> 
> 1.  How important is it to maintain the version-order-checking
> ability that we have with svn?  If it's really important, we'll have
> to incorporate one of the date-based schemes.

Personally, I lean towards seeing it as unimportant, at least if we do
frequent releases to make new features and changes available to other
components. This should be less of a burden with independent releases
and might even help in keeping things release-ready.

Distributed development makes revision versioning pretty much
impossible. IMHO the only addition to the normal x.y.z that makes sense
here is one that clearly identifies a commit. It might be helpful in
some cases. Not neccessarily in a dependency scenario but more in the
"which version/commit of component X or Y do I actually have on my
system?" situation. 

In any case, this kind of revision versioning should only be presented
to the users/developers and not to tools like pkg-config because that
won't work, as we all know by now.

> 2.  How important is it to be able to identify the exact git commit
> that the build is generated from?  If it's really important, we'll
> either need a SHA1 fragment, or we'll need to decide if
> minute-precision (or second-precision) on the date in the revision
> tag is enough.

I guess I answered this one with the above. It might be very helpful
in debugging/testing scenarious to make sure people are on the same
page (e.g. running the same version).

  - Jannis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://mail.xfce.org/pipermail/xfce4-dev/attachments/20090729/390161d8/attachment.pgp>