Releasing Maven 2.0.5

[Graham Leggett]

On Thu, November 2, 2006 4:59 pm, Kenney Westerhof wrote:

> How do we proceed in deciding what to keep and what to move to 2.0.6?
> Bulk change all open issues and move them, then move back some issues
> mentioned
> on this thread and others?

+1.

Regards,
Graham
--



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Brian E Fox]

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:brett@...]
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: dev-unsubscribe@... For
> additional commands, e-mail: dev-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@... For additional
commands, e-mail: dev-help@...




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Jason van Zyl-2]

On 2 Nov 06, at 8:29 PM 2 Nov 06, Kenney Westerhof wrote:

>
>
> John Casey wrote:
>> BTW, I'm in favor of the RC staging, then a vote for that binary.
>
> Yes, me too.
> I want to clarify something:
>
> I wasn't suggesting we release 2.0.5 immediately; I didn't even  
> talk about how/what to release, just that we cut down the number of  
> issues planned for 2.0.5 and start planning a release.
>
> I just created a version for 2.0.6 in JIRA.
>
> How do we proceed in deciding what to keep and what to move to 2.0.6?
> Bulk change all open issues and move them, then move back some  
> issues mentioned
> on this thread and others?
>

I think that's reasonable for the 2.0.5 release. We need to go  
through all the issues again, but to get the 2.0.5 out we need a  
clear picture of what we're going to fix.

+1

> -- Kenney
>
>> -john
>> On 11/2/06, John Casey <casey.john.d@...> wrote:
>>>
>>> Sounds good to me. +1.
>>>
>>> -john
>>>
>>> On 11/2/06, Kenney Westerhof <kenney@...> 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: dev-unsubscribe@...
>>> > For additional commands, e-mail: dev-help@...
>>> >
>>> >
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Jason van Zyl-2]

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:brett@...]
> 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: dev-unsubscribe@... For
>> additional commands, e-mail: dev-help@...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@... For  
> additional
> commands, e-mail: dev-help@...
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[redrackam]

+1

2006/11/2, Kenney Westerhof <kenney@...>:

>
> 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: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

--
Thierry Barnier - cell: 404-771-3048 - tbarnier@...

[Kenney Westerhof-3]

Right now they're both scheduled for 2.1 and seem rather complex.

If you can get them fixed in a week we can definitely push them to 2.0.5,
otherwise we'll wait for 2.0.6, which should come out soon after (talked to
Jason about this).

Is this acceptable? We want to keep 2.0.5 pretty small and start from a clean
slate afterwards.

Mike Perham wrote:
> MNG-2340 and MNG-1577 are both on my must fix list before release.  I
> still need to test the latest patch for 1577.
>
> mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Jason van Zyl-2]

On 2 Nov 06, at 10:26 PM 2 Nov 06, Kenney Westerhof wrote:

> Right now they're both scheduled for 2.1 and seem rather complex.
>
> If you can get them fixed in a week we can definitely push them to  
> 2.0.5,
> otherwise we'll wait for 2.0.6, which should come out soon after  
> (talked to
> Jason about this).
>
> Is this acceptable? We want to keep 2.0.5 pretty small and start  
> from a clean
> slate afterwards.
>

Essentially if you've got an issue and provide a patch and tests it  
has a chance of getting into 2.0.5. We haven't released for a while  
so we are inevitably going to run into some issues with merging, find  
a stable build machine, and fixing a issues listed right now so the  
issue set has to remain small. Do what we can and attempt to release  
the RC a week from tomorrow.

Jason.

> Mike Perham wrote:
>> MNG-2340 and MNG-1577 are both on my must fix list before release.  I
>> still need to test the latest patch for 1577.
>> mike
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Gregory Kick-2]

+1  I've been waiting for the updates to the ant mojo stuff for a while.

On 11/2/06, Jason van Zyl <jason@...> wrote:

>
> On 2 Nov 06, at 10:26 PM 2 Nov 06, Kenney Westerhof wrote:
>
> > Right now they're both scheduled for 2.1 and seem rather complex.
> >
> > If you can get them fixed in a week we can definitely push them to
> > 2.0.5,
> > otherwise we'll wait for 2.0.6, which should come out soon after
> > (talked to
> > Jason about this).
> >
> > Is this acceptable? We want to keep 2.0.5 pretty small and start
> > from a clean
> > slate afterwards.
> >
>
> Essentially if you've got an issue and provide a patch and tests it
> has a chance of getting into 2.0.5. We haven't released for a while
> so we are inevitably going to run into some issues with merging, find
> a stable build machine, and fixing a issues listed right now so the
> issue set has to remain small. Do what we can and attempt to release
> the RC a week from tomorrow.
>
> Jason.
>
> > Mike Perham wrote:
> >> MNG-2340 and MNG-1577 are both on my must fix list before release.  I
> >> still need to test the latest patch for 1577.
> >> mike
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@...
> >> For additional commands, e-mail: dev-help@...
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

--
Gregory Kick
http://kickstyle.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[John Casey]

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...

-john

On 11/2/06, Jason van Zyl <jason@...> 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:brett@...]
> > 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: dev-unsubscribe@... For
> >> additional commands, e-mail: dev-help@...
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@... For
> > additional
> > commands, e-mail: dev-help@...
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

[Kenney Westerhof-3]

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 <jason@...> 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:brett@...]
>> > 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: dev-unsubscribe@... For
>> >> additional commands, e-mail: dev-help@...
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@... For
>> > additional
>> > commands, e-mail: dev-help@...
>> >
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@...
>> > For additional commands, e-mail: dev-help@...
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[topping]

The patch attached to MNG-2626 is 25 lines of code and is easily  
removable.  I would be disappointed if it was not be applied before  
2.0.5 is released.

-b

On Nov 2, 2006, at 1:45 AM, 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: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Dennis Lundberg-2]

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

+1  I'll help with what I can.

--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Rollo, Dan]

Are there any user instructions on how people could kick the tires of a
release candidate AND how to back-out if needed? Given how maven
composes itself on the fly, I'm nervous about trying an RC and finding
out I wasn't really using the right versions, etc. Providing some good
"howto try an RC" steps will help a lot of people quickly evaluate the
release candidate.

Even though I have a few pet issues (especially those related to the Ant
plugin), I think getting a 2.0.5rc out quickly (with only what's fix as
of today) is the way to go. Then see what users find....

Dan (lurking user)


-----Original Message-----
From: Jason van Zyl [mailto:jason@...]
Sent: Thursday, November 02, 2006 10:49 AM
To: Maven Developers List
Subject: Re: Releasing Maven 2.0.5

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:brett@...]
> 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: dev-unsubscribe@... For
>> additional commands, e-mail: dev-help@...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@... For
> additional commands, e-mail: dev-help@...
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@... For
> additional commands, e-mail: dev-help@...
>
>

--------------------------------------------------
This e-mail and any files transmitted with it may contain privileged or confidential information.
It is solely for use by the individual for whom it is intended, even if addressed incorrectly.
If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute,
or take any action in reliance on the contents of this information; and delete it from
your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.
--------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[topping]

On Nov 2, 2006, at 1:59 PM, Rollo, Dan wrote:

> Are there any user instructions on how people could kick the tires  
> of a
> release candidate AND how to back-out if needed? Given how maven
> composes itself on the fly, I'm nervous about trying an RC and finding
> out I wasn't really using the right versions, etc. Providing some good
> "howto try an RC" steps will help a lot of people quickly evaluate the
> release candidate.

All of the composition happens in the repository.  So if you are  
concerned about it getting contaminated, you can move it to a safe  
place, then try the new version.  If you decide you don't like it,  
delete the new repository that was built, move your old one back,  
then run with the old version of maven.

HTH, -b

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Ralph Goers]

Assuming Mike Perham's testing goes OK, I would really like to see my
patch for MNG-1577 in 2.0.5. I cannot move forward with Maven 2 at all
until that issue is resolved.

Ralph

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: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Nathan Beyer-2]

+1 - yes please

I don't know exactly what would be included in a 2.0.5 release, but I
would like to lobby for new releases of wagon providers, etc, so that
the beta-2 version can be included. In particular, the HTTP
compression enhancements would be nice to have.

-Nathan

On 11/2/06, Kenney Westerhof <kenney@...> 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: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[brettporter]

Are you referring to the fix I put in for MNG-1908?

For all my testing, this time it looks ok - no performance problems.  
But I'd really like some others to test this heavily to make sure  
there aren't any side effects I haven't noticed.

- Brett

On 02/11/2006, at 10:00 PM, Stephane Nicoll wrote:

> +1, especially for the SNAPSHOT download issue.
>
> Stéphane
>
> On 11/2/06, Kenney Westerhof <kenney@...> 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: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...