For anyone making the switch from SVN or CVS, the links Ton provided are certainly a must-read. I had set up Mercurial mimicking behavior I was accustomed to with CVS, and whaddaya know, commands I "thought" I understood did not behave like I expected. The concepts of local vs. remote and commit vs. push for repositories are unique to Mercurial, and this feature solves a problem that has always bothered me: protecting my code with revision control, while protecting others against my code.
The main reason I went with Fog Creek for this side project is because they are a reputable company with a free turn-key product that I'm pretty confident is going to be developed and supported for years to come. It does not support any LabVIEW IDE integration, but that's fine for now. I have found Kiln good for only one thing so far: having a reliable, hosted backup of the project (which is all I need it to do). Fogbugz is spectacular, but pretty overkill for what I'm doing. I like to use it for keeping notes on features I might work on, and archiving auto-generated emails from program errors/exceptions. In the future, I plan to use the email system as a public bug/feature communication line.
Overall, I would recommend these turn-key easy-to-configure products, but that's coming from a thus-far casual user.
LabVIEW user groep 