meant to cc: this to the dev list as well. sorry.
----- Forwarded message from J Aaron Farr <[EMAIL PROTECTED]> -----
Date: Fri, 16 Jan 2004 13:04:31 -0500
From: J Aaron Farr <[EMAIL PROTECTED]>
Reply-To: J Aaron Farr <[EMAIL PROTECTED]>
Subject: Suggestions on JIRA Setup
To: [EMAIL PROTECTED]
Hello,
The Avalon community is united in our desire to adopt JIRA (anxious in fact!),
but there's been a lot of discussion about how to track everything. No one in
the group is especially experienced, so I would appriciate any thoughts or
persepectives the JIRA savvy among us can provide.
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!
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.
Thanks!
---
jaaron <http://jadetower.org>
Proposed Avalon projects:
http://marc.theaimsgroup.com/?l=avalon-dev&m=107411983705763&w=2
http://marc.theaimsgroup.com/?l=avalon-dev&m=107412560512495&w=2
Full email thread at:
http://marc.theaimsgroup.com/?t=107401818200004&r=1&w=2
----- End forwarded message -----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
