On Wed, 2011-09-21 at 09:26 -0500, Steve Loranz wrote:
That is to say that I believe the package names should take the
format
version-increment.<date>
where version is the output of 'git describe' which could be:
0.6.1 for a tagged release
or
0.6.1-2-g1eb400d for a version that is two commits past 0.6.1 with a git hash of 1eb400d
I see, that makes sense. I'm understanding from dgoodwin that the tito
project [1] was designed to assist with generating appropriate version
and release information (both official releases and interim builds). I
believe it can help with build submission. My understanding is that it
is being used in other projects (notably katello) to provide that
%{version}-%{release} format you suggest above.
Is anyone experienced with using tito to assist with the packaging
process for each project? Any concerns/objections around investigating
using tito to standardize the build/tag/versioning process across the
different projects?
Thanks,
James
[1]
http://rm-rf.ca/tito