对于Subversion中的版本和项目,什么是好的存储库布局? [英] What is a good repository layout for releases and projects in Subversion?
问题描述
我们有标准的Subversion主干/分支/标签布局。我们有几个分支机构用于中长期项目,但到目前为止还没有一个分支机构。
我们应该:
- 混合发行分支和项目
- 创建发布文件夹?如果是这样,还有比发布更好的名称吗?
- 创建一个项目文件夹并将当前分支移动到那里吗?如果是这样,有没有比项目更好的名字?我在其他存储库中看到过沙箱和尖峰。
- 还有其他东西吗?
易于人们理解
-这样权限管理可能会更容易
而且,顺便说一句:这是一个好主意,几乎没有存储库,而不是很多,因为更改历史记录通常可以通过这种方式更好地保存(如果在存储库之间移动文件,除非采取特殊且有些复杂的操作,否则更改历史记录就消失了)。在大多数设置中,应该只有两个存储库:主存储库和供沙盒用户试用Subversion的沙箱存储库。
project1
树干
分支机构
1.0
1.1
joes-experimental-feature-branch
标签
1.0.0
1.0.1
1.0.2
项目2
树干
分支机构
1.0
1.1
标签
1.0.0
1.0。 1
1.0.2
We have the standard Subversion trunk/branches/tags layout. We have several branches for medium- and long-term projects, but none so far for a release. This is approaching fast.
Should we:
- Mix release branches and project branches together?
- Create a releases folder? If so, is there a better name than releases?
- Create a projects folder and move the current branches there? If so, is there a better name than projects? I've seen "sandbox" and "spike" in other repositories.
- Something else altogether?
I recommend the following layout, for two reasons: - all stuff related to a given project is within the same part of the tree; makes it easier for people to grasp - permissions handling may be easier this way
And by the way: It's a good idea with few repositories, instead of many, because change history normally is better preserved that way (change history is gone if you move files between repositories, unless you take special and somewhat complicated action). In most setups, there should only be two repositories: the main repository, and a sandbox repository for people experimenting with Subversion.
project1
trunk
branches
1.0
1.1
joes-experimental-feature-branch
tags
1.0.0
1.0.1
1.0.2
project2
trunk
branches
1.0
1.1
tags
1.0.0
1.0.1
1.0.2
这篇关于对于Subversion中的版本和项目,什么是好的存储库布局?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!