[Trac] Multiple Subversion projects with single Trac Ticket database

[Gary Oberbrunner]

The other day, Alain wrote:
> 
> Carwyn Edwards escreveu:
>> I have a similar model in terms of libraries and applications but I've
>> done this in a single svn repo:
>> ...
>> It works very nicely with trac as you can have global and per sub
>> element roadmaps (use naming conventions) and components per sub
>> project in the ticketing system.
> 
> Could you be so kind as to give me an example. I have just been thinking
> a lot about naming convention lately. I am just about to start using
> Trac so I would appreciate very much any such help.

I'm also interested in trac naming conventions.  We have a single base product
in a single svn repository, with many subprojects, each with its own
milestones and schedules.

I'm leaning toward a convention like this:
  Trac variable       Our usage
  -------------       -------------------
  component           subproject name e.g. Project1
  milestone           <subproj_name>_<release_number> e.g. Project1_1.0beta1
  version             same as milestone (trac requires this I think)

This way the Roadmap display shows all scheduled milestones for all
subprojects, in completion-date order.  Further, we will define some custom
reports that group tickets and milestones by component and/or show all tickets
for a given component.

I would prefer to have a new "project" or "subproject" field and use component
to further break down the components of each project, and have the Roadmap and
reports group by project, but I don't think this can be done with trac as it
is today without some modification.

We'd also like to save the last-used component in the session object and
prefill new tickets with that default, since one person is likely to be
working on one project at a time.  This seems easy to do, the way the session
table is organized.

Is this naming convention similar to what other folks are using?

thx,

-- Gary Oberbrunner