Quote:You need to understand that the whole GoogleCode page is meant to be a developers' place, so there is really no reason for us to care about complains like "omg I want my rev numbers back!!1".
I respectfully disagree. This change has major implications for the user community, especially the wiki. As the bleeding-edge svn version has been at the very top of the download for some time, I would guess that many users, even newbies, are using the latest code rev on their machines.
Further, Release 3.0 (while a generally excellent rev) is not the best or fastest for every game out there. Until there comes a time when we can say 'Release 5.0 is the absolute best and most compatible at everything', there will be the need to direct users to non-release versions of code. Right now, we do that on the wiki by telling users which range of code versions to use, like this:
The new git rev numbers are not sequential, so there is no way to know if one release comes before another.
I think an easy solution would be to keep a running rev number that increments with each new git commit. I am not enough of a git expert to know whether this would have to be done manually or could be automated, but keeping the same rev sequencing that the users are used to, and the wiki is already coded for, would really help maintain continuity as you guys shift over to git. Otherwise, I have no idea how we're going to adapt the wiki for revs that are not sequential and are very hard to copy for a compatibility rating.
Please consider doing this (or something similar that will allow rev numbers to continue) so that those of us working on the wiki, and those of us doing your regression testing (as you acknowledged), will be able to continue to do so.
Respectfully,
Keller