Howard Lewis Ship schrieb:
Interesting catches. I'm looking for opinions:
a) Fix these in 5.1.
I wouldn't ship a GA release with a *known* buggy feature.
b) Continue with 5.0.15, fix these in 5.0.16, try for 5.0.16 as
release candidate.
That's what I would do, just don't call 5.0.15 a release candidate then. For the future, I'd make
relatively fix release dates and fix everything scheduled for this release. If anything *critical*
comes up that can't be fixed in time I'd postpone the release and fix it, otherwise I'd just
continue with the release schedule. We'll always find something if we just start looking thoroughly
when a release is to be tested or voted upon. That's what the snapshot builds should be for.
c) Abort 5.0.15 (again!), fix these, start again.
I'd only do this if any of these issues are real blockers for any reason.
I beginning to feel like I'm playing wack-a-mole.
I've got a nice big club I could lend you :-)
Cheers,
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
