As I understood Carsten's reasoning, 2.1.5 cannot be released because it
introduces an incompatibility with 2.1.4. Therefore he was recommending NOT
having a 2.1.5 but going to 2.2 instead. 2.1 would basically be dead.
If we follow the rule "retroactively", the possible branch point would be the last Cocoon release 2.1.4 as this would simplify much (no reverts necessary). Good patches could then be applied to 2.1 branch afterwards.
I prefer this way over an incompatible 2.1.5.
Joerg
