Some folks will say: release early, release often.
I agree, unless it's too often and too early.
Don't panic with the first issue of your release. Give users some time to come
with new issues.
Personnaly I just don't like to release for every little thingy. Here it's only
one non-blocker while there are 39 open issues.
I'd say: try to pick up some more issues.
That's just my opinion.
-Robert
> Date: Fri, 22 Apr 2011 13:11:10 -0400
> From: bimargul...@gmail.com
> To: dev@mojo.codehaus.org
> Subject: Re: [mojo-dev] propose cobertura-maven-plugin 2.5.1 to fix
> MCOBERTURA-145
>
> Robert,
>
> I understand your point. At the same time, another spin around the
> crank (once I've got the fix and some tests) would take me about an
> hour, it would clean up the snafu with the JIRA report, and it would
> finish delivering the aggregation support, which was sort of the idea
> that got me started. What's the downside?
>
> --benson
>
>
>
> On Fri, Apr 22, 2011 at 11:58 AM, Robert Scholte <rfscho...@codehaus.org>
> wrote:
> > I don't see the need to rush. It's not a blocker, just a major bug.
> > Regression happens. Just make sure that there's a good IT to fix and verify
> > this issue.
> >
> > -Robert
> >
> >> Date: Fri, 22 Apr 2011 10:12:10 -0400
> >> From: bimargul...@gmail.com
> >> To: dev@mojo.codehaus.org
> >> Subject: [mojo-dev] propose cobertura-maven-plugin 2.5.1 to fix
> >> MCOBERTURA-145
> >>
> >> MCOBERTURA-145 seems to me to justify a turn of the crank, but not a
> >> move to 2.6. Anyone object?
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe from this list, please visit:
> >>
> >> http://xircles.codehaus.org/manage_email
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
