Kaspersky Lab software release stages

1. Beta version. The release of a beta version marks the end of the development process and the beginning of beta testing, i.e. testing by interested users. Beta testing is conducted to try a new application in a real environment and check its compatibility with other software. Internal testing in Kaspersky Lab goes on at this stage.
   
   Errors detected during beta testing are forwarded to developers to be fixed.
   
   Beta version is supported directly by developers via the email address indicated in beta manuals and in the Community beta testing thread.
   
2. Release Candidate. This is a provisional stage of final testing, that can be conducted on Project Manager's request.
   
    Beta version requires a special beta key for activating. Release Candidate can be tested using a common license key. That is, if you are using a commercial version of a product, you can use the license you own for activating a new Release Candidate version of that product.
   
3. Technical Release. This version is technically absolutely complete and operational. Kaspersky Lab partners and clients can receive it.
   
   Technical Release marks the beginning of the final stage of marketing campaign preparation.
   
4. Commercial Release. The beginning of sales of a ready product. From now on the support is handled by the Customer Service department.
   
5. Critical Fix (CF) – an extraordinary release of a new application version/patch that fixes some critical error. CF does not add any new functionality.
   
6. Maintenance Pack (MP) – a scheduled release of a new application version. It adds new functionality and fixes some known issues.