After struggling with multiple (~13) disparate tracs I've built a system to merge them down to two tracs. We're using wiki namespacing (Project/ReleaseNotes), and added a custom ticket field called "Project." We're using the excellent 0.12 MultiRepository branch plus a mercurial forest to keep separation.
This is not the ideal solution, but so far it seems to be the most light weight and flexible method. We think it will serve our needs well, and I'll be sure to post back with experience in a few months. On Tue, Jun 3, 2008 at 11:50 AM, Swiftmind <[EMAIL PROTECTED]> wrote: > My company also has a need for a project hierarchy within Trac. But I must > agree with Jeff Hammel's comment. The core of Trac should be as it is a > minimalist approach but allow a third party program, plug in or whatever to > upgrade Trac easily to a more multi project environment. > > But I have not looked into the current answer of creating multiple Trac > environments. In my opinion if Trac could be upgraded with a simple plug in > to allow a simple project hierarchy within one Trac environment, this would > make Trac much more powerful and desirable. > > -- > __________________________________________________________________ > Eric > Research and Development > OEM Controls Inc. > > > > On Tue, Jun 3, 2008 at 10:08 AM, Jeff Hammel <[EMAIL PROTECTED]> > wrote: > >> >> On Mon, Jun 02, 2008 at 10:17:46PM -0700, Noah Kantrowitz wrote: >> > Macbane wrote: >> >> Hi, >> >> >> >> I have read some of the proposals, for multi project trac. How do >> >> people feel about it, because trac is fine for a small project but >> >> breaks down when you get to a stage where you are working on many >> >> projects at once. Is trac going to support those features or stay the >> >> way it is? How do users feel about it. >> > >> > The very brief overview is that there are some plugins and 3rd-party >> > tools around now that do "heavyweight" multi-project support. This means >> > each project gets its own Environment. The flavor it looks like Trac >> > core will adopt is a much lighter-weight system where most of the tables >> > just get an extra "project" column, and the UI is restructured a bit. >> > Both options have their ups and downs, and I think both will exist in >> > parallel for a while at least. >> > >> > --Noah >> >> This is something that my company has a need for, so I'm curious to hear >> about solutions. Is the TracForgePlugin the "recommended" plugin for this? >> Anything else worth looking at? >> >> As far as "should this go into trac core or in another layer?" I tend to >> favor the latter, both to keep trac core minimalist and also to decouple >> needs, though obviously sufficient hooks need to be in place in order to >> make this work well. But I haven't really looked at the problem space so >> I'll stop running my mouth off now. >> >> Jeff >> >> >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
