<snip/>
My opinion is that we should remove deprecated classes (some of them)
in our 2.1.x branch *now* in order to create a smooth transition and
to build a better basis for the future development.
To indicate this, we should update the version number to 2.2 *now* in
the cocoon-2.1 repository. This would mean that the next Cocoon
version would be 2.2. If the need for a 2.1.5 arises we could still
make a branch.
We clearly indicate that although we have a major version change,
there are only minor incompatibilities that shouldn't affect users.
Who is affected by those changes? What does an upgrade mean for the user?
-- Reinhard
