Though we will get again "endorsed lib problem" questions on the users list, I updated the XML lib jars to their latest releases as in Cocoon 2.1. I hope nobody has something against this. At least we have a good explanation and solution for these issues now (http://wiki.cocoondev.org/Wiki.jsp?page=EndorsedLibsProblem). If the ParanoidCocooonServlet works ok only in Cocoon 2.1 a message shall be added to this wiki page.
But there is another reason for this mail: Now with the current XSLTC we can switch to it as default processor in 2.0 too, can't we?
And what about the using the treeprocessor as default in Cocoon 2.0? If it's on the same status as in 2.1, it seems to be stable enough - even for non-development/milestone releases.
There is small issue with the treeprocessor -- nested action sets (see bugzilla). And Cocoon 2.0 ships with the samples containing those action sets. It would be pretty upsetting to break those samples.
Once this issue is resolved, +1 from me to use treeprocessor.
Vadim