> -----Original Message----- > From: Serge Knystautas [mailto:[EMAIL PROTECTED] > > >>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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
