Subject | Re: [Firebird-general] Re: Oops, we did it again (MySQL 5.1 released as GA with crashing bugs) |
---|---|
Author | Ann W. Harrison |
Post date | 2008-11-30T17:37:50Z |
Martijn Tonies wrote:
longer allowed to control the destiny of "his" project and
kicking out against those who do. Is MySQL 5.1 a really
stellar release? Maybe no. But it is substantially better
than 5.0.x. Are there bugs? Of course. But any large, complex
software product has bugs and new bugs are found, even in old
code. If the standard for a release is no bugs - even no
crashing or wrong answer bugs - there would never be a release,
and that's worse that releasing something that's better than
what's available.
If someone made me king and dictator, I'd say that all crashing
and wrong answer bugs discovered at least six months before
the planned release date would be fixed, and that serious bugs
discovered after that point would be dealt with on a case-by-case
basis, considering whether the bug is a regression, the risk of
the fix breaking something else, and the probability that someone
will actually run into it. But no one is going to make me king
or dictator.
Best,
Ann
>What this confirms is that Monty is one unhappy camper, no
> Then again, this kinda confirms a lot of what I was thinking about the
> internals of MySQL...
>
longer allowed to control the destiny of "his" project and
kicking out against those who do. Is MySQL 5.1 a really
stellar release? Maybe no. But it is substantially better
than 5.0.x. Are there bugs? Of course. But any large, complex
software product has bugs and new bugs are found, even in old
code. If the standard for a release is no bugs - even no
crashing or wrong answer bugs - there would never be a release,
and that's worse that releasing something that's better than
what's available.
If someone made me king and dictator, I'd say that all crashing
and wrong answer bugs discovered at least six months before
the planned release date would be fixed, and that serious bugs
discovered after that point would be dealt with on a case-by-case
basis, considering whether the bug is a regression, the risk of
the fix breaking something else, and the probability that someone
will actually run into it. But no one is going to make me king
or dictator.
Best,
Ann