Go to documentation repository
Documentation for Axxon One 3.0/3.1 version. Documentation for Axxon One 2.0 version
is also available.
On the page:
General information
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.
Overview of the version lifecycle
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:
| Branch | Function | Features |
|---|---|---|
| main | It contains only stable code that has undergone a full cycle of automatic and manual testing |
|
| feature | It is used for development of new features and making major changes |
|
| week | It is used for accumulation, testing, and stabilization of small changes over the course of a week |
|
Technical support
The company guarantees high-quality product support throughout its lifecycle:
- Support eligibility: Purchasing a license key entitles you to full technical support for the entire validity period of the key. For lifetime licenses, support is provided until the official end-of-life announcement of the corresponding version of the software.
- Bug fixes: Critical bugs are fixed only in the latest officially released version of the software. We strongly recommend keeping your installed software up-to-date to ensure system security and stability.
Schedule and types of update releases
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 | Once a quarter | It includes significant new features and architectural changes. It is published on the official website |
| Hotfix release | As needed | It contains fixes of critical bugs and vulnerabilities and improvements. It is published on the official website |
| Patch | As needed | Urgent fixes of critical incidents. It is available upon request through technical support |
Licensing policy with regard to software updates
The company guarantees a simple and predictable update process:
- License compatibility: New versions of the software are fully compatible with license keys from previous versions. Updating your software doesn't require a new key.
- Saving of functionality: After the update, all previously purchased and activated features remain fully available.
- Access to new features: Functionality added in the new version and subject to licensing isn't available until you update the license key.
Compatibility of client and server versions
Attention!
To ensure operation, we recommend using the same client and server version.
| Client version | Server version | Compatibility level | Supported features |
|---|---|---|---|
| Any version of the 3.0/3.1 branch | Any version of the 3.0/3.1 branch | Full compatibility | All features of client and server are fully available. Any combination of minor releases within the 3.0/3.1 branch is supported. For example, client version 3.0.0 is fully compatible with server version 3.0.2. |
| Any version of the 3.0/3.1 branch | 2.0.14 | Basic compatibility | Connection to the server, viewing of live and archived video, search by detector events, metadata, faces and license plates |
| 2.0.14 or earlier version | Any version of the 3.0/3.1 branch | Compatibility isn't guaranteed | Compatibility of the versions hasn't been tested |
| Any version of the 3.0/3.1 branch | 2.0.12 | Compatibility isn't guaranteed | Compatibility of the versions hasn't been tested |
Overview
Content Tools