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 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
