We have a small 3 developer team that is currently using Subversion for our source control. We expect the team to group to 8 members within the next 6 to 12 months. We are considering changing our source control to either TFS or Mercurial for improved branching. I know TFS is overkill for just branching, but that is the immediate need, and the other features of TFS could aid our team. One of our main concerns with TFS is we've heard that there is a lot of overhead deploying it, especially on a small team. I'm hoping to get some community insight into just how much overhead there may be involved, suggestions to make the process easier, and anything else the community may feel is useful in making the decision to implement.
我们有一个小型的3开发团队,目前正在使用Subversion进行源代码管理。我们希望团队在未来6到12个月内分组到8名成员。我们正在考虑将源代码控制更改为TFS或Mercurial以改进分支。我知道TFS对于分支来说是过度杀伤,但这是迫切需要,而TFS的其他功能可以帮助我们的团队。我们对TFS的主要关注之一是我们听说有很多开销部署它,特别是在一个小团队中。我希望能够获得一些社区洞察,了解可能涉及多少开销,使流程更容易的建议,以及社区可能认为在做出决策时有用的任何其他内容。
3 个解决方案
#1
18
In my experience, TFS works really well, even for small teams. If your total number of developers is five or less, you can use the relatively affordable Workgroup edition: above that, you'll have to pony up for the real thing, pricing for which is definitely in the 'Enterprise' realm...
根据我的经验,即使是小型团队,TFS也能很好地运作。如果您的开发人员总数为5或更少,您可以使用相对实惠的Workgroup版本:在此之上,您将不得不为真实的东西付出代价,其定价肯定在“企业”领域......
The biggest hurdle to starting to use TFS is installing the darn thing: this process seems to be designed for maximum aggravation. (The extent to which the 'designers' of the 2005-to-2008 upgrade 'process' despise their users even manages to go beyond that: fortunately, you'll be able to start with TFS2008 and won't have to worry about upgrading for a while).
开始使用TFS的最大障碍是安装这个问题:这个过程似乎是为了最大程度的恶化而设计的。 (2005年到2008年升级'流程'的'设计者'鄙视他们的用户的程度甚至超过了这个程度:幸运的是,你将能够从TFS2008开始,而不必担心升级一阵子)。
If you follow the instructions exactly, you should manage in 2-3 tries, though, and the hardware requirements aren't as bad as they seem. My 3-developer TFS setup runs quite comfortable on a previous-generation Dell laptop with 4GB of RAM.
如果您完全按照说明操作,则应该在2-3次尝试中进行管理,并且硬件要求并不像看起来那么糟糕。我的3开发人员TFS设置在配备4GB RAM的上一代戴尔笔记本电脑上非常舒适。
One of the big advantages of TFS is the VS integration: this works just really, really well, and shelving and branching are implemented in a more straightforward way than with any other systems I've seen.
TFS的一大优势是VS集成:这种方法非常,非常好,并且搁置和分支的实现方式比我见过的任何其他系统都要简单。
The process guidance and support in TFS are a bit less polished, but still quite usable. The pluggable support for several development methodologies is quite nice, and several third-party add-ons (for example for Scrum) are available already.
TFS中的流程指导和支持稍微不那么精确,但仍然非常实用。对几种开发方法的可插拔支持非常好,并且已经有几个第三方附加组件(例如Scrum)。
All in all, it definitely won't hurt to try TFS: if you have a MSDN subscription, you probably already have the Workgroup edition as well as a trial of the full version: otherwise, you can downloaded the latter from Microsoft as well.
总而言之,尝试TFS绝对不会受到影响:如果您有MSDN订阅,您可能已经拥有Workgroup版本以及完整版本的试用版:否则,您也可以从Microsoft下载后者。
UPDATE, April 12th, 2010: With the release of Team Foundation Server 2010, the installation and upgrade procedures have improved a lot. A new TFS2010 install shouldn't take you more than a few minutes (assuming you already have an instance of SQL Server 2008 up and running) and even an in-place upgrade of my TFS2008 setup proved to be entirely painless.
更新,2010年4月12日:随着Team Foundation Server 2010的发布,安装和升级过程得到了很大改进。一个新的TFS2010安装不应该花费你几分钟(假设你已经有一个SQL Server 2008的实例启动并运行),甚至我的TFS2008设置的就地升级证明是完全无痛的。
#2
4
Setup of TFS is not too complicated, when you exactly follow the given guide step by step. We are using it on a small team for about one year now and i don't want to miss it any more.
当您完全按照指定的指南逐步操作时,TFS的设置并不复杂。我们现在在一个小团队中使用它大约一年了,我不想再错过了。
Especially when you use more than one part of tfs like version control and work item tracking and maybe even teambuild, your team will benefit of the tight integration of the seperate parts.
特别是当您使用tfs的多个部分(如版本控制和工作项跟踪,甚至可能是teambuild)时,您的团队将受益于单独部件的紧密集成。
For example, you can link to workitems when checking in code changes. Then you run an automated build with teambuild and it will automatically update your workitems with the build number. So afterwards you can see for example in a bug workitem the buildnumber which contains the bugfix.
例如,您可以在签入代码更改时链接到工作项。然后,您使用teambuild运行自动构建,它将使用内部版本号自动更新您的工作项。所以之后你可以在bug工作项中看到包含bug修复的buildnumber。
We also use the sharepoint wiki for documentation and planning although i'm not the biggest sharepoint fan...
我们还使用sharepoint wiki进行文档和规划,尽管我不是最大的分享粉丝......
The main point is the great integration into the IDE and for workitem tracking the Teamsystem Web Access which allows you to control at least your workitems over a webinterface.
重点是与IDE的完美集成以及跟踪Teamsystem Web Access的工作项,它允许您通过Web界面控制至少您的工作项。
#3
1
It's been awhile, but I'm thinking that it takes about a half-day to get setup, plus some time reading the manuals beforehand to make sure you know what you're doing. Configuration doesn't take too long -- you need to add all of your developers in as licensed users. Setting up projects is not too hard. I usually set up AD groups to map on the project roles and add those groups to the appropriate roles. I set up a new project in about 1/2 hour.
已经有一段时间了,但我认为需要大约半天的时间来安装,加上一些时间事先阅读手册以确保您知道自己在做什么。配置不需要太长时间 - 您需要将所有开发人员添加为许可用户。设置项目并不难。我通常会设置AD组来映射项目角色,并将这些组添加到适当的角色。我在大约半小时内建立了一个新项目。
Note: I don't use any of the features of TFS except source control. If you plan to item tracking, use the project sharepoint site, etc., your mileage will vary quite a bit. I've found that on our projects (2-3 developers) a wiki works just as well for project management.
注意:除了源代码控制之外,我不使用TFS的任何功能。如果您计划项目跟踪,使用项目共享点网站等,您的里程会有很大差异。我发现在我们的项目(2-3个开发人员)中,维基也可以用于项目管理。
#1
18
In my experience, TFS works really well, even for small teams. If your total number of developers is five or less, you can use the relatively affordable Workgroup edition: above that, you'll have to pony up for the real thing, pricing for which is definitely in the 'Enterprise' realm...
根据我的经验,即使是小型团队,TFS也能很好地运作。如果您的开发人员总数为5或更少,您可以使用相对实惠的Workgroup版本:在此之上,您将不得不为真实的东西付出代价,其定价肯定在“企业”领域......
The biggest hurdle to starting to use TFS is installing the darn thing: this process seems to be designed for maximum aggravation. (The extent to which the 'designers' of the 2005-to-2008 upgrade 'process' despise their users even manages to go beyond that: fortunately, you'll be able to start with TFS2008 and won't have to worry about upgrading for a while).
开始使用TFS的最大障碍是安装这个问题:这个过程似乎是为了最大程度的恶化而设计的。 (2005年到2008年升级'流程'的'设计者'鄙视他们的用户的程度甚至超过了这个程度:幸运的是,你将能够从TFS2008开始,而不必担心升级一阵子)。
If you follow the instructions exactly, you should manage in 2-3 tries, though, and the hardware requirements aren't as bad as they seem. My 3-developer TFS setup runs quite comfortable on a previous-generation Dell laptop with 4GB of RAM.
如果您完全按照说明操作,则应该在2-3次尝试中进行管理,并且硬件要求并不像看起来那么糟糕。我的3开发人员TFS设置在配备4GB RAM的上一代戴尔笔记本电脑上非常舒适。
One of the big advantages of TFS is the VS integration: this works just really, really well, and shelving and branching are implemented in a more straightforward way than with any other systems I've seen.
TFS的一大优势是VS集成:这种方法非常,非常好,并且搁置和分支的实现方式比我见过的任何其他系统都要简单。
The process guidance and support in TFS are a bit less polished, but still quite usable. The pluggable support for several development methodologies is quite nice, and several third-party add-ons (for example for Scrum) are available already.
TFS中的流程指导和支持稍微不那么精确,但仍然非常实用。对几种开发方法的可插拔支持非常好,并且已经有几个第三方附加组件(例如Scrum)。
All in all, it definitely won't hurt to try TFS: if you have a MSDN subscription, you probably already have the Workgroup edition as well as a trial of the full version: otherwise, you can downloaded the latter from Microsoft as well.
总而言之,尝试TFS绝对不会受到影响:如果您有MSDN订阅,您可能已经拥有Workgroup版本以及完整版本的试用版:否则,您也可以从Microsoft下载后者。
UPDATE, April 12th, 2010: With the release of Team Foundation Server 2010, the installation and upgrade procedures have improved a lot. A new TFS2010 install shouldn't take you more than a few minutes (assuming you already have an instance of SQL Server 2008 up and running) and even an in-place upgrade of my TFS2008 setup proved to be entirely painless.
更新,2010年4月12日:随着Team Foundation Server 2010的发布,安装和升级过程得到了很大改进。一个新的TFS2010安装不应该花费你几分钟(假设你已经有一个SQL Server 2008的实例启动并运行),甚至我的TFS2008设置的就地升级证明是完全无痛的。
#2
4
Setup of TFS is not too complicated, when you exactly follow the given guide step by step. We are using it on a small team for about one year now and i don't want to miss it any more.
当您完全按照指定的指南逐步操作时,TFS的设置并不复杂。我们现在在一个小团队中使用它大约一年了,我不想再错过了。
Especially when you use more than one part of tfs like version control and work item tracking and maybe even teambuild, your team will benefit of the tight integration of the seperate parts.
特别是当您使用tfs的多个部分(如版本控制和工作项跟踪,甚至可能是teambuild)时,您的团队将受益于单独部件的紧密集成。
For example, you can link to workitems when checking in code changes. Then you run an automated build with teambuild and it will automatically update your workitems with the build number. So afterwards you can see for example in a bug workitem the buildnumber which contains the bugfix.
例如,您可以在签入代码更改时链接到工作项。然后,您使用teambuild运行自动构建,它将使用内部版本号自动更新您的工作项。所以之后你可以在bug工作项中看到包含bug修复的buildnumber。
We also use the sharepoint wiki for documentation and planning although i'm not the biggest sharepoint fan...
我们还使用sharepoint wiki进行文档和规划,尽管我不是最大的分享粉丝......
The main point is the great integration into the IDE and for workitem tracking the Teamsystem Web Access which allows you to control at least your workitems over a webinterface.
重点是与IDE的完美集成以及跟踪Teamsystem Web Access的工作项,它允许您通过Web界面控制至少您的工作项。
#3
1
It's been awhile, but I'm thinking that it takes about a half-day to get setup, plus some time reading the manuals beforehand to make sure you know what you're doing. Configuration doesn't take too long -- you need to add all of your developers in as licensed users. Setting up projects is not too hard. I usually set up AD groups to map on the project roles and add those groups to the appropriate roles. I set up a new project in about 1/2 hour.
已经有一段时间了,但我认为需要大约半天的时间来安装,加上一些时间事先阅读手册以确保您知道自己在做什么。配置不需要太长时间 - 您需要将所有开发人员添加为许可用户。设置项目并不难。我通常会设置AD组来映射项目角色,并将这些组添加到适当的角色。我在大约半小时内建立了一个新项目。
Note: I don't use any of the features of TFS except source control. If you plan to item tracking, use the project sharepoint site, etc., your mileage will vary quite a bit. I've found that on our projects (2-3 developers) a wiki works just as well for project management.
注意:除了源代码控制之外,我不使用TFS的任何功能。如果您计划项目跟踪,使用项目共享点网站等,您的里程会有很大差异。我发现在我们的项目(2-3个开发人员)中,维基也可以用于项目管理。