Hi,
I'm working release planning, and I want to define how we actually
build Maven for a release.
For me it essentially boils down to:
Use the last bootstrap version of the build to produce the version of
Maven for the given release.
I think this lets us remain internally self-consistent, and avoids the
previous release problem. If we use the last stable version of Maven
we get into the problem of requiring all those versions if you really
wanted to start from scratch. I think this makes it self-contained and
will keep the Linux distro people happy because they can build
everything from source.
If no one has any objections I'm going to build this into the release
plan for 2.1 and codify it in Hudson.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]