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
disclaimer: i've just started a new job and won't be spending all that much time on lenya in the next month or so, so ignore me :) i think moving along with cocoon 2.2 is a very good idea. but there are also a number of other things on the agenda: * get rid of areas * revisit content repository * generic editor handlers * 21st century css for the authoring interface * even more ajax. 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). -- Jörn Nettingsmeier "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
