Jörn Nettingsmeier wrote:
Thorsten Scherler wrote:
Hi all,
like sounded in the thread around Cocoon 2.2 FOP NG update we need to
look into updating to cocoon 2.2. Further our famous 1.3 branch that
brings some nice ideas should merge with the 2.0.x branch.
Maybe we can take the chance to merge both branch in an upcoming 3.0.
Would it make sense to have a clean cut?
I meaning starting first with a requirements/architecture document and
ten develop the code around it (using as much good as we have right
now). Do you think it would be possible?
salu2
i wonder: should we really be starting a 3.0 at this point? it seems
weird to spread our (already small) developer base even thinner...
i think we owe it to our users to invest some more time into the 2.0
branch (with easy upgradeability - let's not fool ourselves: a
transition from cocoon 2.1 to 2.2 will *not* be seamless except for the
most trivial of deployments).
I agree. I think with our small developer base we should hold off on
starting 3.0. A roadmap for 3.0 and 2.0 should be generated. Release
early and release often. I think we're probably close to a 2.0.2
release, given several performance updates that happened just after
2.0.1, plus some of the bug fixes.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
