修订控制系统，有哪些可供选择? [英] Revision control systems, which to choose from?

问题描述

大家好，

我正在建立版本控制系统.
我正在寻找你们认为最好的和为什么的观点.
因此，更多的是从那些在这些系统上使用过多个软件的人们那里寻求建议.

问候，


*** !!请投票!! ***

Hey all,

I''m in the process of setting up a revision control system.
I''m looking for opinions on what you guys think is the best and why.
More so looking for advice from people who have worked with more than one on these systems.

Regards,


*** !!Please Vote!! ***

推荐答案

开源，其他一切都太冒险了！即使断定许可证限制的可能性很小，代码断言也非常重要，以至于无法忍受.
同样，由于某些原因，开源系统倾向于非侵入性，这对于商业系统来说是一种问题.

我会投票给Subversion.即使它不是最高级的(未分发)并且确实存在一些问题，它还是最流行且用途广泛的.最重要的是:如果您选择更高级的分布式系统(我会考虑Bazaar，Mercurial，Git)，它将与您的Subversion数据库一起使用-Subversion兼容性被视为主要要求.

最佳系统的选择不是最终决定.您将需要选择一个平台来托管服务，确定您是首选内部服务器还是第三方托管，协议和安全级别设置.通常，每个平台都有一个以上的发行版本.客户部分是每个开发人员的偏好问题.对于Windows上的Subversion，最流行的也许是TortoiseSVN，它也非常不引人注目，它是基于Shell API构建的(这意味着它可以在Explorer或任何其他基于Shell的Commander(如Total Commander)之上运行.主要修订控制系统有(同一团队的)相似产品.也可以使用Visual Studio集成程序包(虽然我不喜欢这种方法).

集市，Mercurial，Git:这些是分布式修订控制系统.这样的系统相对于集中式系统非常有益(请参阅 http://en.wikipedia.org/wiki/Distributed_revision_control [ ^ ]，其中列出了更多系统).我之所以没有在生产中使用它们，只是因为那时Subversion更成熟了.我希望，几年前我看到的缺点可能会消除这些日子(谁有这种经验，请发表评论)，因此这些系统值得认真考虑.

开放源代码修订控制系统的优点在于，修订控制，代码库的完整性和协作至关重要，仅此而已，社区就舔干净了每一个问题，尤其是在数据安全方面.我的意思是，即使我看到软件故障，也可以确定这与我们代码库的安全性无关.而且，与我见过的任何商业系统(惊奇?)相比，文档要好得多.

社区的支持令人惊讶.

Open source, everything else is too risky! Code asserts are too important to suffer even from a very remote possibility of license limitations.
Also, by some reasons, open source systems tends to be non-obtrusive, which is kind of problem with commercial ones.

I would vote for Subversion. Even though it is not the most advanced (it is not distributed) and does have some problems, it is the most popular and quite versatile. Most important thing is: if you choose more advanced distributed system (I would think about Bazaar, Mercurial, Git), it will work with your Subversion database -- Subversion compatibility is considered as a major requirement.

Selection of best system is not the final decision. You will need to select a platform to host the service, decide if you prefer in-house server or 3-rd party hosting, protocol and level of security settings. Usually, there are more then one variant of distribution for each platform. A client part is a matter of preference of each individual developer. For Subversion on Windows, most popular is perhaps TortoiseSVN, it is also very non-obtrusive, build over Shell API (it means it can work on top of Explorer or any other shell-based commander like Total Commander). There are similar products (of the same team) for major Revision Control Systems. Visual Studio integration packages are also available (not that I like this approach though).

Bazaar, Mercurial, Git: those are Distribute Revision Control Systems. Such systems are very beneficial over centralized (see http://en.wikipedia.org/wiki/Distributed_revision_control[^], some more systems are listed). I did not use them in production only because at that time Subversion was more mature. I hope, the shortcomings I saw years ago might me eliminated these days (who has this experience, please comment), so those systems deserve serious consideration.

What''s good about Open Source Revision Control Systems, is that the mere fact that Revision Control, code base integrity and cooperation are so vitally important, the community licks clean every single issue, especially if it comes to data safety. I mean, even if I see glitches in software, I can be sure that is has nothing to do with safety of our code base. Also, documentation is much better compared to any commercial system I ever saw (surprise?).

And the support from community is amazing.

我已经使用了多个系统(SVN，Sourcesafe等).目前，我使用Subversion，它与Visual Studio(通过 AnkhSVN )和Windows( http://www.codeproject.com/KB/dotnet/VistaVisualSourceControl.aspx .

SVN符合我的需求(团队规模，构建工具等).我不认识你有很多优秀的系统，但是如果您自己不进行检查，您将永远不会了解最适合您的需求的系统.

I have worked with several systems (SVN, Sourcesafe etc.). Currently, I work with Subversion and it integrates nicely with Visual Studio (through AnkhSVN) and with Windows (TortoiseSVN). Concerning setup, you can find a few articles on CP: http://www.codeproject.com/KB/dotnet/VistaVisualSourceControl.aspx.

SVN matches MY needs (team size, build tools etc.). I don''t know yours. There are excellent systems out there, but if you don''t check them yourself, you will never learn what best suits your needs.

这篇关于修订控制系统，有哪些可供选择?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！