I see that Cocoon 1.x has started to incorporate features planned for Cocoon 2.x – why?
We believe that smooth project evolution is much better than step-wise revolutionary paths. For this reason, we’ll try hard to incorporate some of the Cocoon2 features in the main project thus limiting the porting effort for you over time. Note that this doesn’t mean that Cocoon won’t change in the future and we state clearly that we do care about back compatibility but only when this is not limiting the evolution of the platform too much. For this reason, while we plan to make the DOM->SAX evolution relatively painless, the sitemap proposal will completely change the Cocoon configurations. Anyway, Cocoon has a long way to go and if it changes during its evolution to a final state, don’t complain: you have been warned. However, we DO consider and value the time you invested in Cocoon so we’ll do our best to make sure that unneeded back incompatibilities don’t get included.
