Why Scala 2.8 instead of Scala 3.0?

Given the size of the changes between 2.7 and the proposed 2.8,  
coupled with the fact that 2.8 is now binary incompatible with 2.7,  
what is the reason for not following accepted version numbering wisdom  
and bumping the major version to indicate a backward incompatible  
change? Why are we targetting 'Scala 2.8' as the next version instead  
of 'Scala 3.0' ? If, as it is to be believed, that this is the last of  
the binary incompatible changes, then starting off with a new Scala  
3.x prefix would make sense, and also give some kind of encouragement  
that the on-going debate on whether Scala is enterprise ready or not.

Alex