Is there a compelling reason to track sites.php with version control? I'm wondering if sites.php is a file that should be tracked?  I can see it being useful because domains tend not to change for any given site (not true for development, as I usually run a shortname.local site alias for ease).  But then again, if you're not tracking the actual site folder, then the site folder name could vary from installation to installation potentially, making tracking sites.php potentially a useless cause...

I don't know, I guess I'm looking for guidance here.  Typically I do not track the sites folder because it contains generated site files and sensitive database information, so maybe it doesn't make sense to track sites.php?

Looking for some tips from the seasoned pros out there.
We track it. You can have more than one entry in sites.php that points to the same site, so we have one for the production site and then a few more for development purposes.

The file is not sensitive itself, because if you give someone the ability to read the contents of .php files on your webserver, then you have bigger problems! I'd say try and find reasons NOT to keep it under version control.

I have to say Gisle's suggestion of manually logging changes to files seems to be a bit more effort than I'd normally want to put in, to get round a problem that's not really a problem for me to begin with!