We have switched all Jitsi projects to GitHub. Git does not have revision numbers like SVN, but commit hashes instead. So far we've been using the SVN revision number as part of the version and as part of the file name of Jitsi deliverables.
For example, a Jitsi version would look like this:
2.3 is the major version number;
4695 is the CruiseControl (or Jenkins) build number;
9822 is the SVN revision.
Here are several possible solutions:
* using the SVN revision number provided by svn.github.com. We actually tried doing this for a while but had some (potentially resolvable) issues. It also requires use of two separate repositories.
* use the git commit count on master. This works with a single repo.
Both of the above however are a bit of a nonsense because the whole point of introducing rev numbers as part of the version string was to allow developers to easily checkout a version that is being reported as problematic. Better yet, it allowed seeing if a problem that's being reported is occurring with a version that has or does not have a specific fix.
This is no longer that straightforward with the above two bullets. A third option would hence be:
* using the short git hash. This could look awkward in a version string though. It also isn't that simple to determine whether one hash is before or after another one but build numbers could help alleviate this.
Finally we could also just:
* drop the fourth component of the revision.
Opinions are most welcome.