Bertrand Delacretaz wrote:
What I fear is that, if we release an evolution of 2.1.x and name it
2.2, people will be confused. For example by searching our lists for
"2.2" and finding lots of messages about Maven, while *that* 2.2
version would not use Maven.
That is a valid concern. We kind of painted ourselves in a box by
calling trunk 2.2 way before it was ready to be anything. However, even
taking trunk in isolation and forgetting the JDK 1.3 issue, I think
trunk is more deserving of 3.0 than 2.2.
Ralph
