Rationale for which bugs make a release?

["Brian E. Fox" <br...@reply.infinity.nu>]

I guess I'm a little confused about how something is decided which
release a fix goes into. Here's a good example: MNG-1898. This is
functionality that was broken between 2.0 and 2.0.1. It is listed as a
blocker and has reproducible test cases associated with it, yet this one
didn't make the 2.0.3 release. The test case has been attached since
just before 2.0.2 was released. 
 
Don't get me wrong, you guys have done geat work, but it's discouraging
to see so many issues get bumped from revision to revision. 

Re: Rationale for which bugs make a release?

[Carlos Sanchez <ca...@apache.org>]

The test case attached doesn't work, there're missing dependencies

On 2/20/06, Brian E. Fox <br...@reply.infinity.nu> wrote:
> I guess I'm a little confused about how something is decided which
> release a fix goes into. Here's a good example: MNG-1898. This is
> functionality that was broken between 2.0 and 2.0.1. It is listed as a
> blocker and has reproducible test cases associated with it, yet this one
> didn't make the 2.0.3 release. The test case has been attached since
> just before 2.0.2 was released.
>
> Don't get me wrong, you guys have done geat work, but it's discouraging
> to see so many issues get bumped from revision to revision.
>
>


--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

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

Re: Rationale for which bugs make a release?

[Brett Porter <br...@apache.org>]

Hi Brian,

Some will be coming back in, but this probably won't be one. It's a
difficult and risky fix with a known workaround (IIRC). It's a shame it
got introduced initially, but now with a test case it will be easier to
maintain after it is fixed.

You're welcome to voice a -1 on the release vote if it is that important
to you. At this point, all it will do is delay the release - it won't
get the issue fixed any faster. The test case will help, patches will
get it fixed even faster :)

Given it is a regression, I would like to think it gets prioritised
properly for a 2.0.4.

The main reason for bringing forward a release was a different
regression in 2.0.2 that was blocking a Continuum release.

- Brett

Brian E. Fox wrote:
> I guess I'm a little confused about how something is decided which
> release a fix goes into. Here's a good example: MNG-1898. This is
> functionality that was broken between 2.0 and 2.0.1. It is listed as a
> blocker and has reproducible test cases associated with it, yet this one
> didn't make the 2.0.3 release. The test case has been attached since
> just before 2.0.2 was released. 
>  
> Don't get me wrong, you guys have done geat work, but it's discouraging
> to see so many issues get bumped from revision to revision. 
> 

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