创建颠覆存储库的最佳实践? [英] Best practice for creating subversion repositories?

问题描述

我们的团队(5-10个开发人员)计划为.NET(Visual Studio)项目/解决方案(VisualSVN Server，TortoiseSVN/VisualSVN)采用Subversion .

Our team (5-10 developers) plans to adopt Subversion for our .NET (Visual Studio) projects/solutions (VisualSVN Server, TortoiseSVN / VisualSVN).

组织新存储库树的最佳方法是什么?可以使用一个大型存储库还是为每个解决方案/产品线等创建不同的存储库更好?

What is the best way to organize a new repository tree? Is it okay to use one big repository or is it better to create different repositories for every solution / product line etc.?

我们的项目可以通过这种方式进行分类(示例):

Our projects can be categorized this way (example):

• 主要产品线
  • 主Web应用
    • 图书馆1
    • 图书馆2
    • ...
    • Main Product Line
      • Main Web App
        • Library 1
        • Library 2
        • ...
        • 工具A
        • 工具B
        • 软件1
        • 软件2
        • 应用1
        • 应用2

        推荐答案

        通常，在任何情况下，如果您期望使用不同的访问权限(例如，某些开发人员应具有对一个项目的提交访问权限，则不能使用该权限)另一个，或者一个项目有一个公共的只读匿名接口，而另一个没有).

        Generally, you want to use a separate repository in any case where you are expecting different access permissions (i.e. some developers should have commit access to one project, but not another, or one project has a public read-only anonymous interface but another doesn't).

        如果不需要那种级别的访问控制，尤其是如果您需要能够在项目之间复制或移动文件(即项目可能共享代码)，则希望将所有内容都存储在一个存储库中.

        You want everything in one repository if you don't need that level of access control, especially if you need to be able to copy or move files between projects (i.e. projects might share code).

        将您的主干/标签/分支拆分放置在与您可能作为单个程序包发布的代码块相对应的任意级别(即，考虑在何处进行标签).刚开始时这并不重要，因为它们在内部与任何其他文件夹都没有不同，因此您可以稍后移动内容，尽管当然没有这个问题比较整洁.

        Put your trunk/tags/branch split at whatever level corresponds to a chunk of code you might release as a single package (i.e. think of where you would tag). This isn't critical to get right at first, since these no different internally from any other folder, so you can just move things around later, though of course it's neater not to have that problem.

        这篇关于创建颠覆存储库的最佳实践?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！