John Casey wrote:
I totally agree with this, except where regressions from 2.0.4 are
concerned. I think there are a couple of issues in there that are going to
break compatibility...I reverted the fix-for version on the one that I
saw a
little while ago, but where there's one...
Yeah I saw that - that's fine. I just bulk moved all issues to 2.0.6, and we
can move issues back in to 2.0.5.
We shouldn't make a release that has regressions. Even if 2.0.5 has less bugs
than 2.0.4, doesn't mean that things that worked in 2.0.4 are broken in 2.0.5,
if we can prevent it.. ;)
Jason, about the release date, 1 week from tomorrow; is that for the rc version?
We definitely will need some people testing it in production systems.
-- Kenney
-john
On 11/2/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I think we just need to release what's there and pick another small
set of issues. The second we say we're going to release everyone
wants a fix here and there which is understandable. I think we should
try and turn out the RC quickly, release and then try again. If we
start trying to fix things like this it could hold up the release for
quite a while. We've got lots of things fixed, so we can toss things
in people think are critical and we'll do what we can in a one week
window. Kick the release out and start with a clean slate again.
Jason.
On 2 Nov 06, at 8:41 PM 2 Nov 06, Brian E. Fox wrote:
> I'm all for a new release, except that we are having tons of issues
> with
> dual-core processors. Something in plexus is causing thousands of
> warnings and worse, it actually builds slower than older single core
> machines. The issue for this is: http://jira.codehaus.org/browse/
> PLX-287
>
> I have been trying to get our build down to a reproducible artifact I
> can send but I'm not quite there yet.
>
> -----Original Message-----
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 02, 2006 6:00 AM
> To: Maven Developers List
> Subject: Re: Releasing Maven 2.0.5
>
> I'm in agreement, but let's do this right - we should designate a
> build
> as an RC and put it out for some testing. If all goes well, we can
> call
> a vote.
>
> Thanks for pushing this forward Kenney.
>
> Cheers,
> Brett
>
> On 02/11/2006, at 8:45 PM, Kenney Westerhof wrote:
>
>> Hi,
>>
>> I've talked to several users in the past period about issues in maven
>> 2.0.4.
>> It's getting frustrating to see users having the same problems over
>> and over again due to bugs that were fixed 5 months ago.
>>
>> There are 53 issues resolved for 2.0.5, and Looking at the number of
>> open issues for 2.0.5, and still 178 to go. With the current rate of
>> resolving issues, 2.0.5 won't be out at least for another 178 / 53
>> * 6
>
>> months = 20 months.
>>
>> I feel that there are enough critical issues resolved for 2.0.5 to
>> warrant a release. Could we start planning a 2.0.6 release and move
>> most of the open issues from 2.0.5 to 2.0.6?
>>
>> Here's my +1.
>>
>> -- Kenney
>>
>>
>> ---------------------------------------------------------------------
>> 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]
>
>
>
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
