> This is exactly why I'd like to put the current trunk code on the path of > being released as 3.0. We have tons of things that could reasonably be > improved in 2.0.x, but aren't really appropriate in such a minor release as > 2.0.11. We could move toward larger feature introductions like import > scope in a more appropriate manner if we were to put those things into a > 2.1.x release. We might be able to put a limit on the lifespan of 2.0.x at > the same time, and only release regression fixes to that branch, and start > working on intermediary efforts to improve Maven from its 2.0.x baseline > without having to accommodate/wait for a full-blown rewrite of all these > major subsystems. >
+100 Arnaud
