On Jan 24, 2006, at 4:32 PM, Gary Oberbrunner wrote:
Just to add my voice to the chorus:
We use a single repository and produce a number of distinct commercial
products from it, all on their own schedules. So we use trac like
this:
* Single trac instance, single repo
* Trac Component -> our Product
* Trac Milestone -> our Milestone, with ProductX_ prefixes.
This actually works OK for us. The main problems are:
* Roadmap intermixes all products (since it doesn't know about
products
at all)
* Trac says "Component" and we just translate in our heads to
"product".
* We'd like to use Components for what they were intended for (UI,
back
end, licensing -- i.e., components of projects.)
* We needed to make a bunch of custom reports to sort tickets by
component, since Trac assumes Versions and Milestones are 1:N with
Components but for us it's kind of the other way around.
* Some of the displays like the Milestone display assume
Components are
used the "regular way" and become less useful for us.
We're doing the same thing, and don't really mind the "component =
product" requirement, but it might be nice to make the expand Trac to
handle multiple products within a single project.
So, "ditto". ;-)
Cheers!
--Chris Ryland / Em Software, Inc. / www.emsoftware.com
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
