Subversion 存储库的推荐布局背后的原因是什么? [英] What is the reasoning behind the recommended layout for Subversion repositories?

问题描述

使用 Subversion 进行版本控制 建议(单项目)存储库采用以下布局(由 这个问题):

/trunk
/tags
  /rel.1 (approximately)
  ...
/branches
  /rel1fixes

与(可能)更面向过程的安排相比，这种安排的相对优点是什么?:

What are the relative merits of this arrangement when compared with a (perhaps) more process-oriented one?:

/development
  /current
  /stable
/qa (maybe)
  ...
/production
  /stable
  /Prod.2
  /Prod.1
/vendor
  /Rel.5.1
  /Rel.5.2

请注意，我正在考虑内部部署，而不是构建产品.

Please note that I'm thinking of in-house deployment, rather than building a product.

免责声明:虽然我是 Subversion 用户，但我从未在真实的现场环境中使用它进行部署.

Disclaimer: although I'm a Subversion user, I've never had to deploy with it in a real live environment.

推荐答案

推荐的布局和您提议的布局之间的主要区别在于，推荐的布局在某种程度上是自我记录的，关于提交的位置以及它的行为方式.

The main difference between the recommended layout and your proposed layout is that the recommended layout is somewhat self-documenting as to where to commit things, and how it behaves.

比如在推荐的布局中，很明显所有的新开发都致力于主干，而且大部分分支都是从主干上做的.此外，很明显，您永远不应该向/tags 提交任何内容.最后，可以安全地假设分支是真正的分支，其中可能包含特定于该特定分支目的的更改.

For example, in the recommended layout, it's obvious that all new development is committed to trunk, and most branches are made from trunk. Also, it's obvious that you should never commit anything into /tags. Finally, it's safe to assume that branches are truly branches, which may contain changes specific to that particular branch purpose.

根据建议的布局，其中一些事情不太确定./development/stable 是从/current 分支的吗?/development/stable 和/production/stable 之间有什么关系?这些目录中哪些是标签，哪些是我可以实际检查的目录?

With the proposed layout, some of these things are less certain. Is /development/stable branched from /current? What's the relation between /development/stable and /production/stable? Which of these directories are tags, and which ones can I actually check stuff into?

当然可以记录这种行为，但是通过坚持每个人都使用的公认布局，您可以更轻松地让新员工了解其工作原理.

Certainly this behavior can be documented, but by sticking to the accepted layout that everybody uses, you'll have an easier time getting new hires up to speed on how it works.

这篇关于Subversion 存储库的推荐布局背后的原因是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！