Am 11.04.2006 um 16:00 schrieb Paul Gaspar:
Just a suggestion from me: It is ok if the beta programm is closed,
but why not publish a public beta or final candidate a week before
the release? Then RS could prevent unusable releases like r2.
That wouldn't have helped in this case: b5, which introduced most of
the problems, was released at 3/31, fc1 at 4/4 and the last final
candidate, fc4 at 7/4. It isn't that the beta list didn't catch those
problems. And what benefits could a three day public final possibly
have?
The quality is the result the two facts: A fixed release schedule and
features which are introduced very late in the development cycle. I
actually tried to make a little fun of that :
Eng. A: We are too weak, we are much too weak!
Eng. B: I could make the compiler much stricter on short notice.
Project Manager: OK, but let us do it one week before final
release. That is much more fun.
Eng. A: Wouldn't it be even funnier, if we would give no helpful
error message?
Project Manager: Yeah, you are the best, A.! I will like that
complaining
CEO: Bonus to all!
Hans-Georg
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
