Releasing Maven 2.0.5

[Kenney Westerhof-3]

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

[mihobson]

+1, more frequent releases the better.

Mark

On 02/11/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@...

[Franz Fehringer]

Any chances for MNG-2305 (only first active proxy considered/used)?

Greetings

Franz


Kenney Westerhof schrieb:

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

[Jason Dillon]

Yes!  Please more frequent releases :-)

+1

--jason


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

[Graham Leggett]

On Thu, November 2, 2006 11:45 am, Kenney Westerhof wrote:

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

+1.

Regards,
Graham
--



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

[davidkarlsen]

Mark Hobson wrote:
> +1, more frequent releases the better.
>
Absolutely - and more frequent releases of plugins too.
It's becoming increasingly hard to "sell in" the maven idea to projects
due to long-lasting outstanding bugs (or outstanding releases).  
I think this would be a lot easier if releases were more often cut off.

--
David J. M. Karlsen - [phone]
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com



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

[brettporter]

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

[snicoll]

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

[Fabrizio Giustina-4]

a big +1, we should definitively try to release more often

fabrizio


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

[jrduncans]

I know it's lame to throw out a pet issue that's unfixed, but I'm
going to do it anyway because it's been such a big problem for me.
http://jira.codehaus.org/browse/MNG-2340 is a critical regression
issue that was introduced in 2.0.4 that has made using mvn
eclipse:eclipse (or the Netbeans plugin) nearly unusable for me and my
coworkers.  I don't know if this issues hasn't gotten enough
attention/support/votes because not a lot of people use
dependencyManagement with child overrides, or just because it was very
difficult to troubleshoot & determine what was happening.  But I hate
to think that, as long as this problem has been around, it might have
to wait for yet another release cycle...

- Stephen

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

--
Stephen Duncan Jr
www.stephenduncanjr.com

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

[jtolentino]

Here's my +1 :-)

On 11/2/06, Stephen Duncan <stephen.duncan@...> wrote:

> I know it's lame to throw out a pet issue that's unfixed, but I'm
> going to do it anyway because it's been such a big problem for me.
> http://jira.codehaus.org/browse/MNG-2340 is a critical regression
> issue that was introduced in 2.0.4 that has made using mvn
> eclipse:eclipse (or the Netbeans plugin) nearly unusable for me and my
> coworkers.  I don't know if this issues hasn't gotten enough
> attention/support/votes because not a lot of people use
> dependencyManagement with child overrides, or just because it was very
> difficult to troubleshoot & determine what was happening.  But I hate
> to think that, as long as this problem has been around, it might have
> to wait for yet another release cycle...
>
> - Stephen
>
> 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@...
> >
> >
>
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>
> ---------------------------------------------------------------------
> 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@...

[Eric Redmond]

double-plus 1!

On 11/2/06, John Tolentino <jtolentino@...> wrote:

>
> Here's my +1 :-)
>
> On 11/2/06, Stephen Duncan <stephen.duncan@...> wrote:
> > I know it's lame to throw out a pet issue that's unfixed, but I'm
> > going to do it anyway because it's been such a big problem for me.
> > http://jira.codehaus.org/browse/MNG-2340 is a critical regression
> > issue that was introduced in 2.0.4 that has made using mvn
> > eclipse:eclipse (or the Netbeans plugin) nearly unusable for me and my
> > coworkers.  I don't know if this issues hasn't gotten enough
> > attention/support/votes because not a lot of people use
> > dependencyManagement with child overrides, or just because it was very
> > difficult to troubleshoot & determine what was happening.  But I hate
> > to think that, as long as this problem has been around, it might have
> > to wait for yet another release cycle...
> >
> > - Stephen
> >
> > 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@...
> > >
> > >
> >
> >
> > --
> > Stephen Duncan Jr
> > www.stephenduncanjr.com
> >
> > ---------------------------------------------------------------------
> > 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@...
>
>

--
Eric Redmond
http://codehaus.org/~eredmond

[Vincent Siveton]

Definitely +1!

I am also agree with Brett's comment.
Moreover, we need to review issues before and I am pretty sure that we
could close some of them (specially doc). I will investigate.

Cheers,

Vincent

2006/11/2, Brett Porter <brett@...>:

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

[mperham]

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

[Wendell]

I'm all +1 for more frequent releases too.  However, this issue goes to the
core of an issue I brought up previously where maven should publish a build
milestone/release schedule similar to eclipse.  For example, no one is
asking the Eclipse platform guys and gals to please make a release because
we have known for months that the next milestone release is tomorrow, Nov.
3.  To me (at least), it would be soooo much more beneficial to end users
and devs if they knew when this stuff was going to happen.  It allows for
planning on both sides.

Wb


On 11/2/06, Brett Porter <brett@...> wrote:

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

[John Casey]

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

[John Casey]

BTW, I'm in favor of the RC staging, then a vote for that binary.

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

[Christian Schulte]

On Do, November 2, 2006 15:09, 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
>

What about MNG-2646 ? I opened it just yesterday. The attached patch needs
an expert's review, of course, but fixes the issue (for me).

--
Christian



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

[ir. ing. Jan Dockx]

Not a developer, but a quick question on the topic: aren't these  
fixes for a large part in plugins, and not in the core?

(As a user, hooray for the release schedule, BTW).


On 2 Nov 2006, at 15:26, Wendell Beckwith wrote:

> I'm all +1 for more frequent releases too.  However, this issue  
> goes to the
> core of an issue I brought up previously where maven should publish  
> a build
> milestone/release schedule similar to eclipse.  For example, no one is
> asking the Eclipse platform guys and gals to please make a release  
> because
> we have known for months that the next milestone release is  
> tomorrow, Nov.
> 3.  To me (at least), it would be soooo much more beneficial to end  
> users
> and devs if they knew when this stuff was going to happen.  It  
> allows for
> planning on both sides.
>
> Wb
>
>
> On 11/2/06, Brett Porter <brett@...> wrote:
>>
>> 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@...
>>
>>

"[…]  my biggest problem is finding out how to do things."
(in a mail on the Maven Users List)

[Kenney Westerhof-3]

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?

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