选择源控制系统:VSS之后的逻辑后续步骤 [英] Choosing a source control system: logical next steps after VSS
问题描述
我过去几个月一直在使用Git并喜欢它。
我研究了如何在企业环境中托管它。考虑到谁使用的Visual SourceSafe,编程ColdFusion中,PowerBuilder中,PHP和.NET一点的,我发现,让我吃惊的一个10人的团队,是Git的服务器工具仍然是相当简陋。
'p> Git的一家公司 - 托管自己的服务器
问题除了SVN之外,还有哪些其他的源代码控制选项是VSS之后的合乎逻辑的下一步?付费选项很好。
东西漂亮的工具,这是不可怕将是巨大的: - )
Perforce(非免费)提供了很多功能和工具。我听说Google使用它。 Perforce提供比SVN更高级的分支和合并功能。
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, programming 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.
这篇关于选择源控制系统:VSS之后的逻辑后续步骤的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!