This document describes the lifecycle, technical support, and update policy for the software solution. It is intended to provide users and partners with a clear and structured understanding of the development processes, update releases, and terms of technical support. This document and policy are subject to change without prior notice.
To ensure maximum stability and predictability, the software development process follows a clearly defined cycle. Each new version of the software sequentially goes through three key stages, corresponding to branches in the repository of the source code:
| Stage | Branch | Description |
|---|---|---|
| Development | feature | New features and fixes are developed in an isolated environment. All changes undergo mandatory code review and testing, protecting the main codebase from unstable changes |
| Stabilization | main | It contains only stable code that has undergone a full cycle of automatic and manual testing |
| Release | stable | It contains the code for the latest official release, which is available for download on the company's website and is used for updates. In the event of critical incidents, patches are built based on this version |
The company guarantees high-quality product support throughout its lifecycle:
To ensure timely delivery of new features, improvements, and fixes, the company keeps to the following schedule of update releases:
| Type of release | Approximate time interval | Description and availability |
|---|---|---|
| Major release | 1–1.5 years | It includes significant new features and architectural changes. It is published on the official website |
| Hotfix release | 3–6 months | It contains fixes of critical bugs and vulnerabilities, improvements, and can also include new features. It is published on the official website |
| Patch | As needed | Urgent fixes of critical incidents. It is available upon request through technical support |
The company guarantees a simple and predictable update process: