blocks|key|4750349|text|在整个过程中，集中式的IMHO并没有任何意义，特别是如果您在谈论团队开发的话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4750350|另一次投票支持Mercurial，不需要在windows和bitbucket.org下设置任何麻烦，它有免费的存储库(可以是私有的)，空间不受限制。|offset|length|4750351|如果您计划在开源项目上工作，git和Github似乎更合适/更受欢迎。但是，如果您还没有涉足DVCS，我建议您从Mercurial和这个很棒的指南开始。|entityMap|0|LINK|mutability|MUTABLE|url|http://bitbucket.org/|1|http://hginit.com/^0|0|T|D|0|0|1U|7|1^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]]|H|$I|$5|J|K|L|A|$M|N]]|O|$5|J|K|L|A|$M|P]]]]

Distributed all the way, there is really no point for centralized anymore IMHO, specially if you are talking about team development.

Another vote for Mercurial, no hassles to setup under windows and <a href="http://bitbucket.org">bitbucket.org</a> has free repositories (that can be private) with unlimited space.

If you are planning to work on a open source project, git and Github seem to be more adequate/popular. However, if you haven't ventured into DVCSs, I recommend you start with Mercurial and <a href="http://hginit.com/">this awesome guide</a>.

blocks|key|4750274|text|你们都会始终如一地使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4750275|就我个人而言，我喜欢变化无常|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

the one that you will all use consistently

[personally, i like Mercurial]

blocks|key|4750302|text|也许最好的答案是“不管你对什么都满意。”即使是在做私人工作的时候，我也用Git。它似乎做了一个相当不错的工作，无论是向上和向下，和我有限的经验，汞差不多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

Probably the best answer is "whatever you're comfortable with." Even when working on personal stuff, I use Git. It seems to do a pretty good job of scaling both up and down and my limited experience with Mercurial is about the same.

blocks|key|4750394|text|我认为你应该选择你觉得舒服的东西。在一个小组中，您将没有不同的代码树(比如Linux内核)，所以中央存储库是可以的。但是，您也可以使用分布式VCS进行此设置。所以我会带着受欢迎程度和个人经验。流行的有SVN、git和Mercurial。您应该决定，哪种方法最适合与您的团队一起使用(经验，您所选择的IDE中的工具支持等等)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

I think you should choose whatever you are comfortable with. In a small team, you will not have different code-trees (like the Linux-kernel), so a central repository is OK. But you can have this setup also with distributed VCS. So I would go with popularity and personal experience. Popular are SVN, git and Mercurial. You should decide, which o them is best used with your team (experience, tool-support in your choosen IDE etc.).

blocks|key|4750441|text|这实际上取决于您的开发人员是否会脱机开发大量代码，但只能在分布式存储库和集中式存储库之间进行选择，因为这是您应该首先做出的决定。然后，如果您认为集中式方法比SVN工作得更好，那么您需要的就是。另一方面，如果您采用分布式方法，而不是使用git，那么即使在windows上，它也已经足够好了，因为现在您有tortoise+git+(svn也存在相同的接口)。另外，不要太依赖IDE支持，因为如果您使用IDE，您可能会感到非常惊讶，而且您可能会发现，不应该提交的文件请由IDE代表您提交。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

It really depends of whether or not your developers are going to develop a lot of code offline or not, but only to choose between a distributed or centralized repository, since this is the first thing you should decide. Then, if you decide that a centralized approach works better than SVN is all you need. On the other side if you go for a distributed approach than go for git, even on windows it's good enough since now you have tortoise git (the same interface that also exists for svn). Also, don't count so much on the IDE support because you might get a nasty surprise if you ever use that, and you might find that files that shouldn't be commit do get committed in your behalf by the IDE.

blocks|key|4750475|text|问你的团队，如果有人想要照顾它。有稳定的系统和负责的人要比没有人关心好的系统好得多，而且没有人能够从备份中恢复它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4750476|如果有这样的人--他已经知道该用什么了，就接受他的决定吧。如果没有-得到一些托管的解决方案。如果所有的开发人员都没有接触过Shell/Linux，那么尝试GIT+(最好的一个)将是非常愚蠢的。|4750477|它还取决于需要阅读/贡献的“非技术”人员的数量。只需确保他们可以使用它，并且有可用的工具。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

Ask your team, if some one want to take care of it. It is much better to have stable system, and responsible person, than good system when none care about it, and none able to restore it from backup.

If there is such person - he will already know what to use, so just accept his decision. If not - get some hosted solution. It would be very stupid try GIT (one of the best) if all of developers never touched Shell/Linux.

It also depends of number of "nontechnical" people, that need to read/contribute. Just make sure that they could use it, and there are tools available.

blocks|key|1009642|text|SVN在工具中得到广泛支持。工具是关键；不同的人会有不同的技能。有些人更喜欢命令行，有些人更喜欢基于IDE的工具，有些人更喜欢图形工具。目前，SVN似乎是最受支持的工具。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1009643|除了那个变化无常的或吉特。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

SVN is widely supported in tools. Tooling is the key; different people will have different skill sets. Some will prefer command line, some will prefer IDE based tools, some will prefer graphical tools. At the moment SVN seems to be the most widely supported tool. 

Other than that Mercurial or Git.

blocks|key|4750536|text|我认为，在小公司，有些事情是集中的，这是有争议的。(例如，考虑场外备份。当你只有两个人在一个项目上工作，他们住在同一栋楼里，而且着火了，分散到两台电脑上可能是不够的。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4750537|然而:有一个部分集中的解决方案并不会限制您在一个集中的系统。您只需使用git或mercurial之类的东西就可以将其推送到外部服务器。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

I think that in small companies there are arguments for having certain things centralized. (Think for example about offsite backup. When you only have 2 persons working on a project and they are housing in the same building and there is a fire, decentralized to all of two computers might not be enough.)

However: having a partly centralized solution doesn't limit you to a centralized system. You can just push to an outside server with something like git or mercurial.

We are bootstrapping a new team of very small size (say 2-5) my question is:
 which type of version control works best for these kind of teams, either centralized or distributed.

version control for small team

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们正在引导一个规模很小的新团队(比如2-5)，我的问题是:哪种类型的版本控制最适合于这类团队，无论是集中式的还是分布式的。

问小型团队的版本控制
EN

回答 8

Software Engineering用户

Software Engineering用户

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问小型团队的版本控制EN

回答 8

Software Engineering用户

Software Engineering用户

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问小型团队的版本控制
EN