|
1. Alpha-version is not a mandatory step; it is intended to let potential users test the product functionality partially. Meanwhile the application is still being developed.
The version is supported by the developers via the e-mail address given in the documentation for the alpha-version.
2. Beta-version. Beta-version release means that the application has been fully developed, and the application is tested by interested users (it is called beta-testing). The main goal of beta-testing is the application testing in real conditions and checking its compatibility with other applications. The testing stage still goes on.
Errors found during the beta-testing, are fixed by developers.
The version is supported by the developers via the e-mail address given in the documentation for the beta-version or in the corresponding branch of the Kaspersky Lab forum.
3. Release Candidate. This is an additional (optional) step of final testing carried out on the decision of the project Manager. NOTE: For alpha- and beta-testing special keys are needed to activate the product.
Release Candidate can be tested with a usual license key. If you are using any product, then in order to test a new product version you can install this application build with the release candidate status with your license key file.
4. Technical Release. Technically complete product build, it is given to the Company Partners and can be available for Kaspersky Lab clients.
Once the product has been technically released, the final stage is preparing marketing materials for the product.
5. Commercial Release. Begin of the product sale. Since this moment the application is supported by Kaspersky Lab Technical Support.
6. Critical Fix (CF) – special release of either a new application build or of a patch which corrects critical errors in the application. New functionality is not added to the application in CF.
7. Maintenance Pack (MP) – planned release of a new application build, in order to add new functionality to the product and to fix the found errors.
|