On 08/07/2008, at 11:59 AM, Brian Fox wrote:
You mean bootstrap first, then use that build to run
release:prepare...?
I would expect release:prepare to be run normally, but the bootstrap
to be used in release:perform if this is the case.
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'm fine with that (I'm also fine with "use the last release and only
the last release of Maven to produce the release").
I think this lets us remain internally self-consistent, and avoids
the previous release problem.
What was 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.
I'm not sure about that, since the bootstrap still downloads a number
of binary dependencies, but they're easily substitutable and it's a
start.
If no one has any objections I'm going to build this into the
release plan for 2.1 and codify it in Hudson.
I'll respond to John's mail directly, but I think there's some issues
with this.
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
