On 28/01/2009, at 9:03 AM, Brian E. Fox wrote:
Normally I would agree on the late change, but it's entirely optional
usage so it wouldn't affect existing builds and I'd like to start
thinking about 2.0.10 being the EOL for 2.0.x.
Given there's already been a good number of fixes for 2.0.11 that
haven't been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is
and having .11 as the EOL is a better way to go - wdyt?
Cheers,
Brett
-----Original Message-----
From: Brett Porter [mailto:[email protected]] On Behalf Of Brett
Porter
Sent: Tuesday, January 27, 2009 5:00 PM
To: Maven Developers List
Subject: Re: releasing 2.0.10?
On 27/01/2009, at 1:45 PM, Brian E. Fox wrote:
Yes, I was actually waiting to look at the stuff oleg put into 2.1
as I
think this should be considered for 2.0.10.
It's a bit late in the cycle to make a major change again IMO,
especially since this has become a bogey release.
I fixed up the enforcer bugs, I think it was just waiting for the
parent
to be released for the new skin.
Col.
On 2.1.0, I think we should just release what's there as 2.1.0, many
people I spoke to aren't able to use it because it's only a milestone
release. It's just as stable as 2.0.10 at this point so we aren't
helping anyone with further milestones when no one is actually
implementing the plan. We should just push it out and move forward.
I was going to suggest the same thing, as this is also a bogey
release :) There are regressions and patches in M2 that probably still
need to be done, which is what I was coming back to. M3 is easy if
Doxia is released - but I think it could be bumped if not. M4 is just
merging and testing. I'm prepared to drop M5 out since even though it
works, we're not going to be infrastructurally prepared to use this
for a while.
Cheers,
Brett
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
