Redmine 的推荐工作流程布兹尔？
我刚刚在我的服务器上设置了Redmine，其中包含一个受bazaar版本控制的项目。
这是现有的工作流程：
- 每个开发人员（包括我自己）从开发主干创建一个分支。
- 开发人员进行更改并提交到他们的分支
- 我将开发人员的分支合并到主干
中将主干导入Redmine后，只有与主干提交相关的消息被注册，但开发人员提交的消息不会被注册。因此，例如，如果开发人员将“修复#2”添加到提交消息中，则它不会关闭问题#2；相反，我必须将“fixes #2”添加到合并后所做的提交中。
我的工作流程是否有问题，或者是否有更好的方法在我当前的工作流程中使用Redmine？
I have just set up Redmine on my server with a project that has been under bazaar version control.
Here is the existing workflow:
- Each developer (including myself) creates a branch from the development trunk.
- Developer makes changes and commits to their branch
- I merge developer's branch into trunk
After importing the trunk into Redmine, only the messages associated with commits to the trunk are registered, but messages committed by by developers are not. Thus, for example, if a developer adds 'fixes #2' to the commit message, it does not close issue #2; rather, I have to add 'fixes #2' to the commit that I do after the merge.
Is there something wrong with my workflow, or is there a better way to use Redmine with my current workflow?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
共享存储库功能#2799 可能会解决您的问题。
此功能仍然开放，但附加了一个补丁似乎可以工作（根据评论）。
功能#2799：支持 Bazaar 的共享存储库（使用 init-repo 创建）
http://www.redmine.org/issues/2799
The shared repository feature #2799 may fix your issue.
This feature is still open, but there is a patch attached that seems to work (according to comments).
Feature #2799 : Support for Bazaar's shared reposetories (created with init-repo)
http://www.redmine.org/issues/2799
您看不到合并修订的原因是，目前Redmine无法处理它们。抱歉我无法给您更有帮助的答案。 :o(
有关详细信息，请参阅以下内容：
The reason you can not see merged revisions is that, at present, Redmine can not handle them. Sorry I can not give you a more helpful answer. :o(
See the following for more information: