SVN 最佳实践 - 在团队中工作 [英] SVN best-practices - working in a team

问题描述

我开始使用 SVN.我知道基本命令并了解基本原理.我想知道是否有人有在团队环境中使用 Subversion 的任何技巧或最佳实践.

I'm starting out with SVN. I know the basic commands and understand the base principles. I was wondering if anyone has any tips or best practices for working with Subversion in a team environment.

我可以看到在提交代码时添加相当冗长的消息的好处，但还有其他我应该记住的事情吗?

I can see the benefit of adding reasonably verbose messages when committing code, but are there other things I should bear in mind?

感谢所有出色的回答 - 他们帮了很多忙.

推荐答案

鼓励频繁提交. 不熟悉版本控制的团队成员可能觉得他们需要将代码保留在存储库之外，直到它有效对".教导每个人尽早承诺并经常尽快发现问题.与其持有代码直到它工作，不如建议你的团队成员为可能破坏主干的功能创建分支.这导致...

Encourage frequent commits. Teammates new to version control may feel like they need to keep the code out of the repository until "it works right". Teach everyone to commit early and often to find issues as soon as possible. Instead of holding code 'till it works, propose that your teammates create branches for feature that might break trunk. That leads to...

建立分支和标记实践.除了功能分支之外，鼓励您的团队成员使用分支修复大型错误.在工作开始和结束时标记主要错误修复.维护生产/质量保证版本的标签(可能还有分支).

Establish a branching and tagging practice. In addition to branches for features, encourage your teammates to use branches for large-bug fixes. Tag major bug fixes at the beginning and end of the work. Maintain tags (and possibly branches) for production/qa releases.

为中继建立一个策略并坚持下去.一个例子可能是，中继必须始终没有错误地构建."或主干必须始终通过所有单元测试".任何还不能达到主干标准的工作都必须在一个分支中完成.

Establish a policy for trunk and stick to it. One example might be, "trunk must always build without errors." or "trunk must always pass all unit tests". Any work that can't yet meet the standards of trunk must be done in a branch.

这篇关于SVN 最佳实践 - 在团队中工作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！