Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (herse.apache.org: domain of david.blevins@visi.com
 designates 208.42.156.9 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <464EED89.6010104@gmx.de>
References: <464EE948.4040906@tuffmail.com> <464EED89.6010104@gmx.de>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4D97C815-3B59-4FA7-974B-1C5B1F9570FF@visi.com>
Content-Transfer-Encoding: 7bit
From: David Blevins <david.blevins@visi.com>
Subject: Re: Separate projects on JIRA
Date: Sun, 20 May 2007 13:17:44 -0700
To: dev@cocoon.apache.org


On May 19, 2007, at 5:28 AM, Joerg Heinicke wrote:

> On 19.05.2007 14:10, Grzegorz Kossakowski wrote:
>
>> I would like to know your opinions on having multiple project on  
>> JIRA for Cocoon.
>
> If you have a look at [1] you'll see that Jira knows the concept of  
> category. And like Avalon, Geronimo or whatever have multiple  
> projects in their category it should be no problem to have the same  
> for Cocoon.

Not sure what kind of setup you guys have going on, but for stuff I  
work with seems like for every "pool of version numbers" you more or  
less have to have a Jira project.  At least that's why Geronimo has  
those projects -- each of those projects follows its own stream of  
version numbers.

-David