1. Alpha version. This stage sometimes is skipped. It is intended to let potential users test the product functionality partially while the application is still being developed.
The version is supported by developers themselves via an e-mail address indicated in alpha-version documentation.
2. Beta version. The release of a beta-version means that the application has been developed, and is now available for testing by interested users (beta-testing). The main objective of beta-testing is trying the application in real conditions and checking its compatibility with other applications. At the same time Kaspersky Lab also keeps testing the application.
Bugs found during beta-testing are subject to fixing by developers.
The version is supported by developers themselves via an e-mail address indicated in beta-version documentation or in a special branch of Kaspersky Lab forum.
3. Release Candidate. This is an optional stage, a final testing carried out by decision of the Project manager.
While alpha- and beta-testing require special activation keys, a Release Candidate version can be tested using a common license key. So if you want to test a new version of the product you are using, you can install a Release Candidate version and activate it using your existing license key file.
4. Technical Release. A technically complete version provided to Kasperky Lab Partners and (possibly) clients.
The release of a Technical Release version opens the final stage of preparing marketing materials for the product.
5. Commercial Release. Start of product sales. From this moment the application is supported by Kaspersky Lab Technical Support.
6. Critical Fix (CF) – an extra release of a new application version / patch fixing a critical error in the application. A CF does not add new functionality to the application.
7. Maintenance Pack (MP) – a scheduled release of a new application version, adding new functionality to the product and fixing known errors.