Hi,
I really like the idea of trac but I'm struggling a bit with how to leverage it in our environment. Before I start I realize the multi-repository/multi-branch support is not in there yet but I think there may still be a way to use it. Like many companies we have a few different projects and releases being worked on at the same time. Currently code is spread over a few different subversion repositories, no specific reason for that and they could all be merged. But in terms of releases we will typically have major new development going on in one branch and maintenance of the current release going on in another. We have CONTROLLED branches for each release and developers will create branches off the CONTROLLED to make a fix for that release and these branches then get merged back when completed. The branches are CONTROLLED because the only way developer branches can be merged back is after a successful code review. The dev branches get automatically merged back into the CONTROLLED when approved. We have more or less abandoned trunk and release off the CONTROLLED (don't want to start a religious war about that ;-). Note that this is not all working just yet but I had implemented all this with ClearCase at my previous job so I know that its "a good thing". My question for the list is whether anyone can see how I can use trac for at least part of this? I can roughly map the releases to milestones but then ideally I would want a timeline for each CONTROLLED branch. Creating a project for each doesn't work too well since I definitely don't want tickets defined only in that scope..... Anyone have any ideas? thanks, Greg _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
