Quote:
Originally Posted by metalhomicide
Actually we're in Alpha.  Alpha is when features are being added in, Beta is when the all the features are in and everything is being fine-tuned. Then, once it's all right, it's released!  |
Also, many projects will have a Release Candidate(RC) phase before official release and after the beta. Many of the Drupal projects I work with run with an RC before a 1.0 is dropped.
0.30 (?core3?) <---- SWG EMU is prolly still about here to beta, depending of the feature in question
1.0a <---- implementaion of features
1.0b1 <---- bug testing and fixes (I wouldn't call SWGEmu beta, as only a small part of the features are in test, not the entire EMU.
1.0RC1 <---- for final polishes before a release
1.0X Pub <---- this is where public servers take it up unless they begin with an earlier development version
It's not beta until all the features are implemented and being tested against all other features. A Beta is a complete package with hella wrinkles in the wrapping. Once all the bugs appear to be substantially handled a RC is released for last minute tests. If there are no critical bugs, then you can drop a Final release, otherwise you drop a RC2 and run it again, rinse, repeat until you have a solid stable. Granted there will be bugs at Release and un-implemented features, but in large commercial projects things tend more toward thorough testing before a 'supported' release.