The current debate surrounds having individual projects for all "versioned" products versus composite projects for product groups. If we actually have one JIRA project per individual versioned product (usually a jar artifact), that could put us at 60 some projects!
You do want to tie each releasable (versioned) product to a project in JIRA. The advantage of this is that it can help you build the roadmap and changelog when you do a release of that product/project in JIRA. If releases are [always/almost always] timed together, then you could have those products share the same project and tracked as different components.
It does leave you with a ton of projects, but project categories help make that somewhat manageable.
Perhaps that is the way JIRA is supposed to work, but as far as I am concerned,
it seems like overkill. Even maven's setup over at codehaus seems rather
excessive to me. Could someone close to JIRA provide some feedback on this sort
of usage? Perhaps some guidelines could be added to the JIRA FAQ on the wiki. If it turns out that having 40 - 60 projects for Avalon is the right way to go,
then I'll definitely support it. But I want to be sure before we create a mess.
I'll go track down the JIRA Wiki page and add these notes.
-- Serge Knystautas President Lokitech >>> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
