On 08/08/2008, at 5:45 AM, 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.
I'm totally in favour of this.
Toolchains was the best example of how a feature can be well executed
on the 2.0.x codebase. There's also the parallel downloads as Wendy
mentioned, and that is mostly the kind of thing I'd like to focus on.
There are other things that would just be a complete mess to try and
implement there (for example, the checksum verification from the
repository security proposal), and I'd much rather track Mercury and
get involved there at the opportune time for that.
As long as features and fixes come with integration tests that can be
run against 3.0 we can keep feature parity.
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
