bazaar 共享存储库 vs 共置分支 vs 堆叠分支
我需要为 4 名开发人员创建集市工作区。 每个开发人员都将在其本地计算机上工作，并将从其本地分支到网络位置的分支将在每次提交时更新（在自动镜像插件的帮助下）。
此外，网络上的一个分支用于由集成商“推送”的正式版本。
目前，我正在为我的工作区（本地和网络）使用共享存储库，一切运行良好。
但我仍然不明白两件事：
- 共享存储库概念与共置分支和堆叠分支之间有什么区别。它们更适合我的工作空间吗？
- 共享存储库和功能分支之间的唯一区别是功能分支会在共享存储库中自动创建主干分支吗？
I need to create bazaar workspace for 4 developers.
Each developer will work on its local computer and will have branch from its local branch to a network location that will be updated each commit (with the help of auto-mirror plugin).
In addition , one branch on network used for formal versions that being "pushed" by the integrator
Currently i'm using shared repository for my workspace (both in local and network) and all is working well.
But i'm still dont understand two things:
- What is the differences between shared repository concept to colocated branches and stacked branches. are they better fit for my workspace?
- is the only difference between shared repository and feature branches is that feature branches auto create the trunk branch inside the shared repository?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
共享存储库只是用于实现共置分支和功能分支工作流程的核心 bzr 功能。基本上，它是一个包含修订池的目录，每个分支都有子目录，这些子目录的元数据指向池中的特定修订，该修订是该分支的提示。
共置分支和功能分支之间的区别在于，共置分支将所有分支元数据放在与共享存储库和工作树相同的目录中，而功能分支为每个分支拥有单独的子目录和自己的工作树。
您应该使用哪一种取决于您的开发环境。如果您的环境使得在不同目录之间切换变得困难，例如，如果您的脚本具有硬编码的工作树路径，那么您应该使用并置分支工作流程。如果您的环境最好为每个分支拥有完全独立的工作目录，例如需要很长时间才能重新生成的大量编译输出，那么功能分支工作流程可能会更适合您。
A shared repository is just the core bzr feature used to implement the colocated branches and feature branches workflows. Basically, it's a directory that contains a pool of revisions, with subdirectories for each branch that have metadata pointing to a specific revision in the pool that is the tip for that branch.
The difference between colocated and feature branches is that colocated branches has all the branch metadata in the same directory as the shared repository and working tree, whereas feature branches have separate subdirectories for each branch with their own working trees.
Which one you should use depends on your development environment. If your environment makes it difficult to switch between different directories, e.g. if you have scripts that have paths to your working tree hard-coded, then you should use the colocated branches workflow. If it is better for your environment to have completely separate working directories for each branch, e.g. large amounts of compiled output that take a long time to regenerate, then the feature branches workflow would probably work better for you.