Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 12358 invoked from network); 14 Jan 2004 18:41:37 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 14 Jan 2004 18:41:37 -0000 Received: (qmail 54953 invoked by uid 500); 14 Jan 2004 18:41:21 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 54880 invoked by uid 500); 14 Jan 2004 18:41:20 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 54820 invoked from network); 14 Jan 2004 18:41:20 -0000 Received: from unknown (HELO mail6.fw-bc.sony.com) (160.33.98.73) by daedalus.apache.org with SMTP; 14 Jan 2004 18:41:20 -0000 Received: from mail1.sgo.in.sel.sony.com (mail1.sgo.in.sel.sony.com [43.130.1.111]) by mail6.fw-bc.sony.com (8.8.8/8.8.8) with ESMTP id SAA21634 for ; Wed, 14 Jan 2004 18:41:23 GMT Received: by mail1.sgo.in.sel.sony.com id SAA03989; Wed, 14 Jan 2004 18:41:22 GMT Received: by us-sd-xims-1.am.sony.com with Internet Mail Service (5.5.2650.21) id ; Wed, 14 Jan 2004 10:41:22 -0800 Message-ID: <03334AAF1DF8D2119B1000A0C9E32F58065EFAF5@us-pb-xmsg-2.am.sony.com> From: "Farr, Aaron" To: "'Avalon Developers List'" Subject: RE: [PROPOSAL] Adopting JIRA Date: Wed, 14 Jan 2004 10:41:26 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: Serge Knystautas [mailto:sergek@lokitech.com] > > >>if every TLP has a dozen projects the jira will be difficult to > >>navigate > > > > You don't need to see everything in Jira. Just configure your dashboard > fot > > the projects you want to track. In the case of something like Avalon, > if > > there was a request to create Merlin, Frameworks and whatever, we could > > create an Avalon program category, and then you could use the category > > portlet to select the Avalon projects. > > You will want to create a separate project for each product you want to > release. The motivation for this is that JIRA can easily create > changelogs and roadmaps based on versions (changelogs = issues assigned > to a released version, roadmaps = issues assigned to an unreleased > version). Well, the whole product list can be seen from our distribution directory at: http://www.ibiblio.org/pub/mirrors/apache/avalon/ Which is more than I think we want to handle initially. After some thought, he's my two proposals: The Minimalist Approach: Avalon <-- framework, docs, meta, repository, logkit, etc. Components <-- cornerstone + excalibur Fortress Phoenix Merlin The Moderate Approach: Avalon <-- framework and docs Meta Repository Excalibur Cornerstone Fortress Phoenix Merlin LogKit The other issue would be with things currently in the sandbox or incubation like the IDE tools and the C# implementation. Thoughts? J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org