单独使用SVN还是在小型工作组中使用SVN-工作流方法? [英] Using SVN alone or in small workgroups - workflow approach?

问题描述

我已经花了几个月的时间在Web应用程序上工作，我们已经接近生产阶段.现在是时候让此项目的1-3人扩大开发团队了.

I have spent some months working on a web application and we're come close to production stage. It's soon time to expand the development group with 1-3 people on this project.

我在使用SVN方面没有太多经验，但是显然这是大部分较大公司的选择，因此我猜测SVN的优点无疑会超过花在提交/检查上的时间签入/签出等.

I have not too much experience on working with SVN, but It's obviously the choice for a big part of the larger companies out there, so I am guessing that the pros of SVN without a doubt outweights the time spent on commit/check ins / check outs etc.

使用SVN似乎工作流程变得有些复杂，即使我已经阅读了Oem Reilly Media的 Subversion版本控制，而且我不确定使用SVN进行过大杀伤力在单独开发或在一个小型(1-3人)工作组中进行开发时，除了备份之外，还有其他原因吗?

The workflow seems to become a bit more complicated with SVN, and even though I have read Version Control with Subversion by O'Reilly Media and I am not sure yet if it's overkill to use SVN for any reasons besides backup when developing alone or in a small (1-3 people) workgroup?

您如何做到的?单独工作或在小型工作组中使用版本控制的工作流程是什么?

谢谢！

推荐答案

像任何SCM一样，肯定比备份要更多.

Like any SCM, it's definitely for more than backup.

1. 您可以标记特定的发行版，以便在组成发行版的所有代码中标识一个点.
2. 您可以管理不同同时发布的分支，例如如果您需要在开发解决方案的新版本时管理发行版的错误修复程序.
3. 您可以管理多个开发人员，并使用SVN的合并功能来处理并发更改，以使您的开发人员不会踩到彼此的脚趾，也不会覆盖或擦除彼此的更改.

没有SCM，我不会自行开发，更不用说与其他开发人员一起开发了.这是您工具箱中的核心工具，值得早日获得成功.

I don't develop on my own without an SCM, let alone together with other developers. It's a core tool in your toolbox and worth getting au fait with sooner than later.

我的工作流程是什么?这取决于所使用的团队和SCM.

What's my workflow ? It depends on the team and the SCM being used.

1. 如果SCM很好地支持它(例如Git)，我将为每个错误/功能创建一个分支. SVN的分支不是那么热，所以这可能不适用.
2. 我定期签入/合并 .如果您不经常这样做，那么代码库将与您的工作代码库有所不同，并且随后的合并将变得更加困难.此外，您希望团队成员对自己的工作有了解.
3. 我的持续集成过程(例如，我使用诸如TeamCity/Cruisecontrol/Hudosn之类的持续构建引擎)将构建/测试，并在成功的构建/测试周期内选择标记发布.
4. 我将为最终版本创建一个分支，并将在发布后对其进行维护.

1. If the SCM supports it well (e.g. Git), I'll create a branch per bug/feature. SVN is not so hot at branching, so this may not apply.
2. I check in/merge regularly. If you don't do this often, the codebase will diverge from your working codebase, and a subsequent merge will become more difficult. Additionally, you want your team members to have visibility of what you're doing.
3. My continuous integration process (e.g. I use a continuous build engine such as TeamCity/Cruisecontrol/Hudosn) will build/test and optionally tag a release upon a successful build/test cycle.
4. I'll create a branch for a final release, and will work off this for maintenance following release.

这篇关于单独使用SVN还是在小型工作组中使用SVN-工作流方法?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！