您如何在Trac中处理多个(重叠)项目? [英] How do you handle multiple (overlapping) projects in trac?

查看:89
本文介绍了您如何在Trac中处理多个(重叠)项目?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们正在使用笔迹,并且对此感到非常满意.但是,trac开箱即用,仅最适合单项目环境.我很想听听人们为使它与多个项目一起使用而采取的各种方法以及他们的经验.有没有推荐的插件?是否有任何补丁,调整或其他内容?您甚至可能使用的是完全不同的Bug跟踪系统,该系统提供了Trac的所有功能以及多项目支持?

We are using trac and are really satisfied with it. However, out of the box, trac is best suited for single-project environments only. I'd be interested to hear about the various approaches people take to make it work with multiple projects nevertheless and their experiences with them. Are there any plugins to recommend? Any patches, tweaks or whatnots? Are you maybe even using an entirely different bug-tracking system that offers all of trac's functionality plus multi-project support?

我们最近开始自己管理第二个项目,该项目通常可以正常运行,但也有一些缺点,特别是在两个项目重叠的情况下,这是因为我们编写的在两个项目中使用的通用库代码.您如何处理?

We recently started managing a second project ourselves which generally works okay but also has some drawbacks, especially where the two projects overlap because of common library code we wrote that is used in both projects. How do you handle this?

(我将以我们当前的方法作为对此帖子的答案.)

(I'll attach our own current approach as an answer to this post.)

推荐答案

我们采取的方法是为每个新项目创建另一个追踪环境,并设置 Trac.ini 文件.

The approach we took is to create another trac environment for each new project and set up InterTrac links for simpler cross-referencing between the two. We also use a common base Trac.ini file via the [inherit] directive.

除了问题中提到的共享代码的歧义性问题外,还有一些缺点可能会或可能不会影响您,具体取决于您的项目和工作流程的性质:

Besides the ambiguity issues with shared code mentioned in the question, this has a couple of drawbacks that may or may not affect you, depending on the nature of your projects and your workflow:

  • 创建新项目并非易事;无法通过浏览器界面完成
  • 票号不是统一的:每个新项目环境都从#1重新开始-至少使用InterTrac别名,您可以轻松消除它们的歧义
  • 在安装和配置插件时,您必须格外小心,以便在所有环境下都可以安装和配置插件

这篇关于您如何在Trac中处理多个(重叠)项目?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆