in audacity.h ~ line 41, make beta & “stable” lines end with TDATE like “alpha” does (which adds the BUILD date–and thus some commit version info); also change the trailing - (dash) to a space–it looks better IMVHO:
The devs would really like to be able to ID the commit revision number for some bug reports. Search Bugzilla for “commit”–I asked if there was a way and got “No, but it sure would be nice”. Having the build date on the betas (the “stable” is well known but you might as well have it for the sake of completion) as you already do on the alphas (it is part of the string which gets put at the top of the log) would help pin it down to a single day. That way parsing the commits would be a whole lot simpler.
I do not see how the user in the field can then tell the dev what the commit revision number is. I think your example adds a revision number to a source file; they want a revision number on the executable and a way the user can report it in a bug report.
If the source file in question is AboutDialog.cpp:
EDIT: Oops, I was too fast! That will only show the revision when AboutDialog.cpp was last changed.
You’ll need svnversion and a bit of external processing to get the global revision number into your file.
Certainly, because of the freeze. But there will be nightlies going forward, right? And if those nightlies had at the top of the log the latest commit number, I’d know for sure what I’m testing.
As an aside, I can’t see the date/time stamp of commits in Google Code. All I can see is e.g. “Today (26 minutes ago)” or “Yesterday (27 hours ago)”. I can infer from that the UTC of the commit, I suppose, but having it displayed would be much easier, and deal with the issue that was raised when I commented on bug 334 http://bugzilla.audacityteam.org/show_bug.cgi?id=334#c45 .
True, it just extends the ability to tell the build date to beta (and “stable” though of little interest there). Deducing a nightly’s commit revision number from it’s build date is not too hard I would suppose.
In re. searching the Bugzilla, sorry , can be of little further help, I recall it as Richard but maybe Leland who bemoaned the lack.
Build date is already added to alphas and is un-necessary for releases. It seems that it isn’t possible to programmatically add the svn revision number to About Audacity (and so to the top of the log). So I don’t think this is for PFR’s.
Of course the person packaging the “Nightly Builds” (myself for Windows and Paul for Mac) can manually add the svn revision number to the name of the file to be downloaded (or somewhere else). I don’t think it would be acceptable to manually mess with Audacity.h each time to get the revision number in About Audacity and log. Paul might be able to script the file name to also include the revision number - I’ll ask him.