#2086: better support for multiple repositories
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner: cboos
Type: enhancement | Status: assigned
Priority: normal | Milestone: 0.11
Component: browser | Version: devel
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by anonymous):
I have a number of developer subgroups that will each use TRAC+SVN
repos for each package they develop. I'd like a rollup
TRAC that covers the whole project. Each individual package
has interwoven milestones, requirements, and dependencies that
make project tracking at the individual package level very difficult.
Having a top-level (project-level) TRAC is the obvious solution to
this problem. Each subgroup could then follow the TRAC that they are
concerned with and maintain the package TRACs with their own resources.
The project-level TRAC would then pick up meta-data from each individual
package-level TRAC, and track source code for multi-package applications.
We may also depend on a third party partner that also uses TRAC+SVN, and
they will also depend on us. It is a tight partnership, and I would
expect
we could use the project-level TRAC to recieve information from their
project TRAC as well. It would be especially useful to see a project-
level
rollup in the timeline, milestones, and roadmap. I believe this is similar
to the essence of what is being requested above -- I just wanted to
emphasize
a key feature that I believe is missing in the current version of TRAC.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/2086>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
