Bazaar 推荐的工作空间布局

发布于 2024-11-06 23:51:56 字数 260 浏览 1 评论 0原文

我正在尝试设置目录结构(工作空间布局),我需要分离“稳定”和“开发”代码,并且有多个版本。我发现了这个 推荐的 Mercurial 存储库/文件夹结构SVN 用户 这在 Bazaar vcs 下可能吗?还有其他正确构建目录的建议吗?

I am trying to setup directory structure (workspace layout), I need to separate "stable" and "dev" code, and have several releases. I found this Recommended Mercurial repository/folder structure for an SVN user
Is this possible under Bazaar vcs? Any other suggestion to correctly structure directories?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

守护在此方 2024-11-13 23:51:56

这对 Bazaar 来说应该可以正常工作。例如:

my-project (Bazaar shared repository[1])
+ trunk (you can use this for dev if you like)
+ branches (normal directory)
  + v1 (branch for a specific version)
  + v2 
+ stable (push the stable stuff in here)

您可以使用您喜欢的任何目录结构,但是使用 svn 布局有助于使项目中使用 svn 的其他人保持一致。

使用 Bazaar 就像使用 Mercurial 一样,你并不真正需要分支
对于每个版本,因为如果您从主干或马厩中释放
然后你可以只标记它,这基本上设置了一个指向修订版本的指针。尽管为每个系列保留一个分支很方便,您可以将小错误修复推送到该分支上,作为该系列的下一个错误修复版本的一部分发布。

[1] 将项目的基目录设为 Bazaar 共享存储库,这样每个分支就不会保留修订历史记录的副本,而是将所有历史记录存储在存储库中。您可以使用 bzr init-repo /path/to/my-project 创建 Bazaar 存储库,它也会为您创建目录。该目录下推送或分支的所有分支都将自动使用共享存储库。

That should work fine with Bazaar. eg.:

my-project (Bazaar shared repository[1])
+ trunk (you can use this for dev if you like)
+ branches (normal directory)
  + v1 (branch for a specific version)
  + v2 
+ stable (push the stable stuff in here)

You can use whatever directory structure that you like, but using the svn layout helps to make things consistent for others on your project that have worked with svn.

With Bazaar like with Mercurial you don't really need branches
for each release because if you release off of trunk or stable
then you can just tag it which basically sets a pointer to the revision. Although it is handy to keep a branch per series onto which you can push minor bug fixes to be released as part of the next bugfix release for that series.

[1] Make the base directory for your project a Bazaar shared repository, so that each branch does not keep a copy of the revision history but in stead store all the history in the repository. You can create a Bazaar repository with bzr init-repo /path/to/my-project which will create the directory for you too. All branches pushed or branched under that directory will automatically use the shared repository.

能否归途做我良人 2024-11-13 23:51:56

You can also read the official Bazaar documentation on organizing branches and advanced shared repository layouts.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文