Problems that I have had in a professional mixed ability office:
- Mutable History.
You can do some really silly (and powerful) things with Git. This can cause source loss.
- Auto Merging.
This is the best feature of Git. But, we had to shut development down for a week to find the source code that went missing. MSVS has a happy issue with randomly changing line endings and if you don't pull from the repository regularly it gets confused, and changes get lost.
- Push/Pull order.
ClearCase handles the date ordering and history for you, but Git ignores it.
- Staging.
ClearCase (at least UCM) handles branch promotion and other things for you. Git does not. You will have to manage this carefully.
- $ID$
Does not exist for Git. Version tracking from actual releases and problem finding from knowing what the version of the source file is will have to be handled manually. (I am not sure what your release process is.)
For you final code repository, I might suggest a release repository, either another source control system or a separate Git repository, that is managed and only accepts pulls.
I am currently using Git for my solo project, and it is fine. But, in a mixed-ability house with a variety of editors I would be careful. You can really blow you foot off without knowing with Git.
I have not used either, Mercurial or Bazaar. It might be worth looking at these as some of the problems go away, and they have features to mitigate some of the above problems.
