On Mon, 16 Jun 2003 07:34, Greg Meyer wrote: > I'd like to get some clarity on what the official differences are > between a beta release and a release candidate. Also, what is the > difference between a freeze and a deep-freeze and how do those terms > relate to beta vs. rc?
I interpret the terms to mean: Alpha: We know it's broken and probably badly but would really like you to test it as an assembly (distinct from testing the parts). IMESHO, Mandrake should have one alpha release at the start of the RTM cycle. We're willing to make significant changes (bumping versions etc) to make everything work well, so now is the time to squawk loudly if your pet package or feature looks like being left out. Beta: It's probably broken, don't use it in production but please feel free to use it for light duties. We're unwilling to nudge package versions but will do so to fix problems. Minor problems that a lot of effort to be fixed and/or may upset other things in the fixing are now at risk of being left as they are. RC: We think this one may fly. Please subject it to very heavy testing. If it works, it will be blessed and printed to zillions of ISOs. We won't nudge versions at all except as necessary to fix a showstopper. We won't fix anything if it's much less than a showstopper unless it's dead easy and carries no risk of breaking anything else. Release: It's bug-free. Why does everything have rainbow edges? (-: Cheers; Leon
