Subversion 和修订工程 - 什么是最好的网络资源？
我们正在从 CVS 迁移到 SVN，并采用某种修订管理，以强制开发/测试/发布周期的顺序。 我们目前正在同一代码行上进行测试、开发和发布，我们知道这是一种不好的做法，我们希望结束它。
您使用源代码树的经验、知识和建议是什么？
我们正在构建小型/平均（2-5 个月）定制项目，我们必须尽早让客户进行审查。 需求蔓延很常见。
编辑： 请注意，我不仅需要有关颠覆的建议，还需要更多关于如何在主干/分支/标签/版本等中反映整个开发/测试/部署周期的建议
We are migrationg from CVS to SVN and embracing some kind of revision management in order to enforce order to development/testing/release cycle. We are currently testing, developing and releasing on the same code line, we know its a bad practice and we want to make end to it.
What are your experience, know how, suggestions working with source code tree.
We are building small/average (2-5 months) custom projects and we have to give early access to customer for review. Requirement creep is common.
EDIT:
please note, i need not only advice on subversion, but more on how whole devel/test/deploy cycle is reflected in trunk/branches/tags/versions etc
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
...关于这个主题，缺乏好的读物，但如果我必须向一家完全涉足 SCM 的商店推荐一本书，那就是 Vincent Maraia 的《The Build Master》。 它的细节非常简短，但易于阅读，并提供了（非常非常简短）SCM 好主意的概述，一旦您了解它们，这些好主意就会很有意义，但由于某种原因，许多商店完全缺乏这些想法。
祝你好运！
... There is an lack of good reading on this subject, but if I had to recommend one book to a shop completely green in SCM it would be "The Build Master" by Vincent Maraia. It's very short on details but easy to read and provides a (very very brief) overview of SCM good-ideas that make great sense once you know them but which for some reason so many shops completely lack.
Good luck!
Subversion 比 CVS 更容易分支（在 GIT 中分支甚至更便宜）。 我建议您创建分支进行重大修改，并有计划地将分支合并回主干。 要小心不要长时间不合并回分支，因为等待的时间越长，事情就会变得越来越困难。
如果您需要快速启动，并且不想管理所有服务器/设置内容，还有提供集成错误跟踪/部署等的服务：
一些资源：
这本书回答了我最初提出的很多问题：
http://www.pragprog.com/titles/svn/ pragmatic-version-control-using-subversion
在 stackoverflow 上进一步搜索：
TortoiseSVN 的良好分支和合并教程？
Cal Henderson（开发人员Flickr.com）我参加的迈阿密 FOWA 演讲：
http://cdn4.libsyn.com/carsonsystems/Cal_Henderson.mp3
免费的 Subversion“圣经”（关于合并的章节）：
http://svnbook.red-bean.com/en/1.1/ch04。 html
Subversion makes it easier to branch than CVS (in GIT branches are even cheaper). I recommended that you make branches for major revisions, and have a planned merging of the branches back into the trunk. Be vary careful of going long periods of not merging back into the branch, as you it will become more and more difficult the longer you wait.
There are also services out there that provide integrated bug tracking/deployment etc, if you need to get off the ground quickly, and don't want to manage all the server/setup stuff:
Some resources:
This particular book answered a lot of the questions I had initially:
http://www.pragprog.com/titles/svn/pragmatic-version-control-using-subversion
Searching Further on stackoverflow:
Good branching and merging tutorials for TortoiseSVN?
Cal Henderson (developer at Flickr.com) Presentation at FOWA in Miami that I attended:
http://cdn4.libsyn.com/carsonsystems/Cal_Henderson.mp3
The Free "Bible" of Subversion (Chapter on Merging):
http://svnbook.red-bean.com/en/1.1/ch04.html
一个非常好的源代码控制资源：
A very good resource for source control :