Before I read this I noticed the revision had changed on SO from the SVN revision to 2010.4.23.1. Just switched to Mercurial from SVN myself and hit this same problem. We used to display the SVN revision on the site, but now that we have no true central repository, displaying a number that can be tied back to the source control system is a challenge.

How is the reverse date format for the site revision managed and then tied back to source?

2 Answers
2

It's not a perfect system and I am actually looking for a better Cc.net labeller that would relate a build back to a mercurial changeset ID. It must be numeric so that we can include this number in our assemblies at build time.

The 63 is only valid as long as your central repo is never replaced, correct? I don't know why this would happen, but I suppose it could. This is what I decided to do with our source...but it bugs me. :)
–
ranomoreApr 26 '10 at 17:34

@ranomore: Yes, it could. Never rely on the 63. Rely on the e20247... -- that one identifies the changeset no matter what way it reached whichever repo. The idea of DVCS is that there is no real central repo -- it should be replaceable anytime.
–
balpha♦Apr 26 '10 at 17:46