Hi
while our GitHub move is proceeding fine, I miss hardly the consecutive
revision number of Mixxx.
Especially if we move ahead and release alpha test, every tester will
hardly understand what is the difference between
<https://github.com/mixxxdj/mixxx/commit/e1f6cd9f2e2a539ed2d675c1f0213821522585f0>e1f6cd9f2e
and 87bcffbf9bb ...
Or should he better test 17facf9bfe6?
We can solve it with Jenkins, if we integrate the Jenkins build number, but
that is not the same, because the number does not directly depends on the
source itself and it is not reproachable for client builds.
I have just found out, that GitHub actually has a consecutive revision
number for every repro.
You can query it using the Subversion api like that:
svn info https://github.com/mixxxdj/mixxx/ | sed -ne 's/^Revision: //p'
Compared to the Bazaar revno, which was unique for a single branch, the
Subversion Revision Number is unique for the whole repository.
Unfortunately (as far as I understand) this number can only queried
directly from GitHub and is not included in a local git clone. So it looks
like this is unhandy for our approach.
So what do you think, Is this number a suitable replacement for bzr revno?
Is there a smart way to include this number in our target builds. Can we
use git hooks for this job?
Or is there a better Idea?
https://bugs.launchpad.net/mixxx/+bug/1192288
Kind regards
Daniel
<https://github.com/mixxxdj/mixxx/commit/e1f6cd9f2e2a539ed2d675c1f0213821522585f0>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
