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 <[EMAIL PROTECTED]> wrote:

Sounds good to me. +1.

-john

On 11/2/06, Kenney Westerhof <[EMAIL PROTECTED]> 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]

Reply via email to