Release cycle

A Rolling Release

Frequency: A rolling release is updated every 4 to 6 weeks. This regular schedule ensures that users consistently receive the latest improvements and features without significant delays.
Features: This type of release includes all newly developed features. Users can expect to find enhancements and new functionalities with each iteration, thereby keeping the software cutting-edge and aligned with the latest developments.
Patches: In terms of maintenance, security patches related to Common Vulnerabilities and Exposures (CVE), as well as bug fixes, will be integrated into the next release. This approach allows for a proactive response to any identified vulnerabilities, ensuring the software remains secure.

Frequency: A production release occurs every 6 months. This schedule provides a more stable and predictable update rhythm, allowing organizations to plan their upgrades and ensure compatibility with existing systems.
Support Duration: Once a production release is rolled out, it is supported for a duration of 9 months. During this period, users can expect assistance and updates to address any issues that may arise, thereby promoting reliability and user confidence in the software.
Patches: Throughout the support lifecycle, there will be one release every 4 to 6 weeks specifically dedicated to security patches and bug fixes. This strategy ensures that any critical vulnerabilities or bugs discovered after the release are quickly addressed, thereby minimizing risks and enhancing system performance.