单独使用 SVN 还是在小型工作组中使用 SVN - 工作流程方法？
我花了几个月的时间开发 Web 应用程序，我们已经接近生产阶段。很快就需要将该项目的开发团队扩大到 1-3 人。
我没有太多使用 SVN 的经验，但它显然是大部分大公司的选择，所以我猜测 SVN 的优点毫无疑问超过了在提交/签入/检查上花费的时间 。
SVN 的工作流程似乎变得有点复杂，尽管我已经阅读了 O'Reilly Media 的《Version Control with Subversion》，而且我还不确定使用 SVN 是否太过分了 单独开发或在小型（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.
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.
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?
How do you do it? What's your workflow with version control while working alone or in small workgroups?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
不，这并不过分。版本控制对于编程来说至关重要，无论是单独进行、在小团队中还是在大团队中。它消除了对进行“错误”更改的恐惧，因为您随时可以返回到之前的修订版本。它会记住为什么要通过提交消息进行更改。它知道一起改变了什么。还有更多
No, it's not overkill. Version control is vital for programming, regardless if it's alone, in a small or in a big team. It removes fear of doing a "wrong" change, as you can always go back to previous revision. It remembers why a change was done with commit messages. It knows what was changed together. And many more
与任何 SCM 一样，它的用途绝对不仅仅是备份。
没有SCM我不会自己开发，更不用说和其他开发者一起开发了。它是您工具箱中的核心工具，值得尽早使用。
我的工作流程是什么？这取决于团队和所使用的 SCM。
Like any SCM, it's definitely for more than backup.
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.
What's my workflow ? It depends on the team and the SCM being used.
布莱恩的回答没什么可补充的。作为替代方案，您可能想看看分布式源代码控制系统 (DSCM)，例如 Mercurial、Git 或 Bazaar。恕我直言，它们非常适合小型开发人员团体，非常易于设置，但仍然能够扩展到大型项目。
由 Joel Spolsky 撰写的有关 Mercurial 的优秀入门教程可以在 http://hginit.com/ 中找到。
（来源：hginit.com）
There's not much to add to Brian's answer. As an alternative you might want to take a look at distributed source control systems (DSCM) like Mercurial, Git or Bazaar. IMHO they are a perfect match for small developer groups, very easy to setup but nevertheless manage to scale to big projects.
A good introductory tutorial about Mercurial, written by Joel Spolsky, can be found at http://hginit.com/.
(source: hginit.com)