Choosing a source control system: logical next steps after VSS

I've been using Git for the past few months and love it.

I looked into how to host it in a corporate environment. Considering a 10 person team who use Visual SourceSafe, programm开发者_如何学Cing in Coldfusion, Powerbuilder, PHP and a bit of .NET, I found, to my surprise, that the Git 'server' tooling is still fairly rudimentary.

Git in a company - hosting own server

Question Apart from SVN, what other source control options would be a logical next step after VSS? Paid options are fine.

Something with nice tooling, that isn't scary would be great :-)

---

Perforce (non-free) offers a lot of features and tools. I heard Google uses it. Perforce offers more advanced branching and merging capabilities than SVN.

---

There are several Git hosting services that provide Web interfaces and integrated project management, and some of them are targeted at corporate development teams. ProjectLocker and Codebase are two of these. Both Assembla and Github offer a installable version of their server software, so that you can run a private instance of their service.

---

I think Team Foundation Server would be the next logical step up from Visual Source Safe. You can also check out SourceGear Vault as another alternative to VSS.

---

Not a direct answer (as I'm an advocate of SVN myself), but take a look at Wikipedia's entries for List of revision control software and Comparison of revision control software. It will give you something to investigate while you wait for answers here and you might find something little-known that just fits the bill for you. :)

---

Team foundation server, I believe is one that has been tossed around.

---

TFS Basic

---

I'd go with SVN or CVS. Big community and lots of tools and documentation.