Andre Schnabel wrote:
Hi,

Guido Ostkamp schrieb:

Yes, that's clear to me. However I did expect that OOF680_m1, after calling it officially a "beta" is complete though it is not an "RC" yet.

What do you mean with "complete"?

By "complete" I mean all scheduled corrections and new features have been included. I wouldn't call anything "Beta" if there are still things scheduled to be included.

Quoting from wikipedia (http://en.wikipedia.org/wiki/Development_stage#Beta):
A *beta version* or *beta release* usually represents the first version of a computer program <http://en.wikipedia.org/wiki/Computer_program> that implements all features in the initial requirements analysis <http://en.wikipedia.org/wiki/Requirements_analysis>. It is likely to be useful for internal demonstrations and previews to select customers, but unstable and not yet ready for release.

I think, we are perfectly in line with that description. All features are in, most of the patches and bugfixes have been integrated. If we really think that there is *nothing* left to integrate, we have an RC.

André

Just the opposite! Can't be called "beta" because a lot of things are *not yet integrated* (wikipedia states "...that implements all features..."). RC is when, after a beta period (all the planned features and fixes were tested, and regression bugs fixed) you prepare a "before final" version, RC, that is expected to have no more regressions bugs. In a perfect world, RC will become the final release, since beta testing were exhaustive. Just happens that since many people wait for RC to do some tests, in the RC phase we have some more regression bugs, so have multiple RCx. So, in my opinion, we have to reach 0 bugs left (not only integrated) before reach the "beta" stage, let people test, fix regressions, produce beta2, wait and fix, when no more regressions are found, go for RC1, wait, and if is OK go for Final, otherwise for RC2 and so on.
Regards
Marco Menardi

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

Reply via email to