Context Navigation

Version Numbering

Terminology Definitions

Alpha¹

Alpha software is feature-complete but sometimes only partially functional.

Alpha releases are expected to be unstable, perhaps a little unsafe, but definitely usable. They can have known bugs and kinks that have yet to be worked out. Before releasing an alpha, be sure to keep in mind that alpha releases are still releases and people are not going to be expecting a nightly build from the SVN source. An alpha should work and have minimal testing and bug fixing already finished.

Beta¹

Beta software is feature-complete and functional, but is in the testing cycle and still has a few bugs left that need to be ironed out.

Beta releases are general expected to be usable and slightly unstable, although definitely not unsafe. Beta releases usually preclude a full release by under a month. They can contain small known bugs but no major ones. All major functionality should be fully implemented although the exact mechanics can still be worked out. Beta releases are great tool to whet the appetites of potential users by giving them a very realistic view of where your project is going to be in the very near future and can help keep interest by giving people something.

Release Candidate

Release candidates should be testing of the final version. Nothing should change during this phase. It is for stability testing only and to make sure that everything is worked out. The only fixes to ever be committed during release candidate phase is a blocker (i.e. something that fixes required functionality, or a security vulnerability). These should be rare since the purpose of alpha and beta phases is to find them.

Version Definitions