Our most senior developer is a big fan of version control systems and he installed Bazaar so we could try it for a while before migrating new projects to it - unfortunately, we had to stop in the middle because the Maven release plugin doesn't integrate very well with Bazaar and the plugin is more important than using Bazaar instead of Maven now.
It works pretty well, let me say that. One of the major pains that I found when working in a team are conflicting changes, and also the fact that you should not commit a change to the central repository until the change is actually ready to be committed. With Bazaar, I can commit my changes locally and then, when I am ready to do so, I can commit all those changes back to the central repository. I never loose my unresolved conflicted changes (with SVN, you have to resolve it before you can submit it).
I didn't test this, but even getting the changes back from the central repository into your local repository (with your local changes) should be easier with Bazaar. What the experts say is that, as branching/ merging is way easier to be maintained with Bazaar, you won't be afraid of it anymore.
Also Bazaar allows you to work directly with SVN repositories using bzr-svn plugin. You can find more information on this workflow in the guide Using Bazaar on Subversion projects.
Bazaar's biggest strength over all other system is its flexibility.
For example, developers can work in either traditional centralized mode, or they can work in the newer-style, distributed mode. Oh, and they can do it simultaneously on the same repository. Oh, and they can switch back and forth as much as they like.
Bazaar also has two things which are fairly rare to version control systems: excellent documentation and available commercial support.
For me, Bazaar has the most flexibility, best documentation and in general just works. Those things are far more important to me than the fact pulling a branch would be 10 seconds faster with git for example.
发布评论
评论（6）
与 CVS 或 SVN 的主要区别在于 Bazaar 是一个 DVCS（分布式版本控制系统），而不是 VCS：
请参阅集中式版本控制系统和分布式版本控制系统之间的比较，
您可以在此维基百科条目中看到一个很好的功能矩阵。
任何 DVCS 都需要比经典 VCS 更复杂的工作流程，即使您可以使用 DVCS 复制“中央”存储库模型：
（来源：infoq. com)
The major difference with CVS or SVN is that Bazaar is a DVCS (Distributed Version Control System), not a VCS:
see Comparison between Centralized and Distributed Version Control Systems,
and you can see a good feature matrix in this Wikipedia entry.
Any DVCS will require a more complex workflow than a classic VCS, even if you can replicated the "central" repo model with a DVCS:
(source: infoq.com)
我们最资深的开发人员是版本控制系统的忠实粉丝，他安装了 Bazaar，因此我们可以在将新项目迁移到其中之前尝试一段时间 - 不幸的是，我们不得不中途停止，因为 Maven 发布插件集成得不太好与 Bazaar 配合得很好，而且该插件比现在使用 Bazaar 而不是 Maven 更重要。
它运作得很好，让我说一下。我在团队中工作时发现的主要痛苦之一是冲突的更改，而且在更改真正准备好提交之前，您不应该将更改提交到中央存储库。借助 Bazaar，我可以在本地提交更改，然后，当我准备好时，我可以将所有这些更改提交回中央存储库。我永远不会丢失未解决的冲突更改（使用 SVN，您必须先解决它，然后才能提交）。
我没有对此进行测试，但使用 Bazaar 甚至可以更轻松地将更改从中央存储库返回到本地存储库（带有本地更改）。专家所说的是，由于使用 Bazaar 更容易维护分支/合并，因此您将不再害怕它。
Our most senior developer is a big fan of version control systems and he installed Bazaar so we could try it for a while before migrating new projects to it - unfortunately, we had to stop in the middle because the Maven release plugin doesn't integrate very well with Bazaar and the plugin is more important than using Bazaar instead of Maven now.
It works pretty well, let me say that. One of the major pains that I found when working in a team are conflicting changes, and also the fact that you should not commit a change to the central repository until the change is actually ready to be committed. With Bazaar, I can commit my changes locally and then, when I am ready to do so, I can commit all those changes back to the central repository. I never loose my unresolved conflicted changes (with SVN, you have to resolve it before you can submit it).
I didn't test this, but even getting the changes back from the central repository into your local repository (with your local changes) should be easier with Bazaar. What the experts say is that, as branching/ merging is way easier to be maintained with Bazaar, you won't be afraid of it anymore.
您可以在 文档部分，查看最新稳定版本的文档（截至 2010 年 3 月为 bzr 2.1）：< a href="http://doc.bazaar.canonical.com/bzr.2.1/en/" rel="nofollow noreferrer">http://doc.bazaar.canonical.com/bzr.2.1/en/
有：
迁移指南，涵盖以下主题：
此外，Bazaar 还允许您使用 bzr 直接使用 SVN 存储库-svn 插件。您可以在指南中找到有关此工作流程的更多信息 在 Subversion 项目中使用 Bazaar。
You can read tutorials and comparisons of bzr to CVS and SVN at the official Bazaar VCS site in the Documentation section, check the documentation for the latest stable release (which is bzr 2.1 as of March 2010): http://doc.bazaar.canonical.com/bzr.2.1/en/
There is:
Migration Guide which covers such topics as:
Also Bazaar allows you to work directly with SVN repositories using bzr-svn plugin. You can find more information on this workflow in the guide Using Bazaar on Subversion projects.
Bazaar 相对于所有其他系统的最大优势在于其灵活性。
例如，开发人员可以在传统的集中式模式下工作，也可以在更新式的分布式模式下工作。哦，他们可以在同一个存储库上同时执行此操作。哦，他们可以随意切换。
Bazaar 还有两个对于版本控制系统来说相当罕见的东西：优秀的文档和可用的商业支持。
对我来说，Bazaar 拥有最大的灵活性、最好的文档，而且总体来说很有效。这些事情对我来说远比使用 git 拉取分支要快 10 秒这一事实重要得多。
Bazaar's biggest strength over all other system is its flexibility.
For example, developers can work in either traditional centralized mode, or they can work in the newer-style, distributed mode. Oh, and they can do it simultaneously on the same repository. Oh, and they can switch back and forth as much as they like.
Bazaar also has two things which are fairly rare to version control systems: excellent documentation and available commercial support.
For me, Bazaar has the most flexibility, best documentation and in general just works. Those things are far more important to me than the fact pulling a branch would be 10 seconds faster with git for example.
Bazzar 在具有大量历史记录的大型项目上运行缓慢（来自 Emacs 源的 bzr 登录文件需要 1 分钟！）。
并且 http:// 协议效率低下（专为本地网络连接而设计，任何远程操作至少需要约 5 MiB 的流量）。
Bazzar work slow on large project with huge history (bzr log on file from Emacs sources take 1 minute!).
And have inefficient http:// protocol (designed for local net connection, require ~5 MiB of traffic at least for any remote operation).
查看 Bzrinit，了解 Bazaar 分布式版本控制的简要介绍。
Check out Bzrinit for a gentle introduction to distributed version control with Bazaar.