We also got this response:
Jeff Turner pisze:
Hi,
On Wed, Jun 27, 2007 at 01:14:33AM +0200, Grzegorz Kossakowski wrote:
Hello,
At Apache Cocoon development mailing list we are currently
discussing[1] division of Cocoon's JIRA project. There are two reasons
for a such move:
1. We are starting to release smaller parts more independently so we
need different version sets
I don't think splitting the COCOON project is a good idea..
From what I see, you've arbitrarily divided Cocoon modules into areas of
functionality ("core", "database", "forms" etc) and want a separate
project for each. From a JIRA modelling POV, the only advantage of
splitting these into separate projects is so each can have their own
versions, components and release process (release notes, etc).
Joerg Heinicke wrote:
On 10.07.2007 04:57, Grzegorz Kossakowski wrote:
Even more, INFRA people are little unwilling to fulfil what we ask
for so I think it's crucial to have a strong support from our community.
Can they neglect or deny our project's needs? It's ok they put them
into question, but from the points you made it should be rather clear
we need the dividing into multiple projects. They made a point with
the prefix which we can address with the COCOON prefix. So should
there really still be any problem?
Joerg
