Re: [releases] Nominating issue 87709 showstopper 2.4.1 and BEA300

[Uwe Luebbers]

Hi Drew,

Yes, that could be correct if is the decicision of the
release status meeting would be to nominate it as a blocker.
But only if this issue still occurs in 3.0 and that will
not happen.
There is an automated process in place that clones all issues
that we fix in 2.4.1 for the next codeline.
That is what meant with my last sentence below.

Uwe

Drew Jensen wrote:

Uwe Luebbers wrote:

Hi all,

I think this is for sure a blocker for 2.4.1, because
it is a regression from 2.3.1 and that fits the definition
of a release blocker.
But I do not think it can be a blocker for 3.0 Beta.
3.0 Beta is not meant to be a product for a working
enviroment, it's more a showcase for the next upcoming
version, like Beta's for other products.
With the existing easy workaround, I think a problem
like this could not block a Beta.
Beside that, it will be fixed for 3.0 too if we fix
it in 2.4.1.

Uwe

Extending it further then, if this would be a blocker for 2.4.1 and not 3.0 beta, it would become a blocker for 3.0 at the RC stage if not fixed by then. Would that be correct?

Thanks

Drew

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]