John Casey wrote:
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.
-john
I have to agree with this. I'm working on a fix for a jira issue right
now, and while it will be completely compatible it is really an
enhancement, not a bug fix. Since 2.0.x should be in a state of just
getting critical bug fixes it is uncomfortable adding them to the
branch. But since I really need this enhancement, under the current
circumstances I'd end up having to do that. I suspect the same is true
with whatever the issue is that is currently preventing the 2.0.10 release.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
