Releases Lifecycle
Uxopian aims at providing a predictable and disciplined release lifecycle designed for enterprise environments that require stability, long-term visibility, and continuous improvement and bugfixes without operational disruption. Because the various products from its portfolio comes from different origins, they take the following as a direction, and progressively implement toward it.
Release Cadence
Biennial Enterprise Baseline ( Long-Term Support, LTS)) Versions A new Major version of the Uxopian Suite is released every two years (e.g., LTS 2026, LTS 2028). LTS versions are the recommended baseline for all production deployments.
Monthly Stability Updates Supported LTS versions receive monthly updates that focus exclusively on:
- Security concerns
- Defect resolution
- Stability and performance improvements
- Incremental enhancements delivered behind feature flags
This ensures continuous improvement and bugfix delivery while preserving release predictability.
Note: While Fast2, Uxopian AI and ARender are on this cadence, Flowerdocs stability updates are yet sparser and will gear toward a monthly cadence in the coming years. You can refer to the shared calendar for more details.
Bi-Annual Premium Service Packs Exclusively for Premium Support customers, Uxopian designates two specific Stability Updates per year as Service Packs. These releases serve as stability checkpoints, allowing enterprise teams to budget their QA and validation efforts on a predictable six-month cycle.
Customers deploying a Service Pack benefit from a dedicated six-month patch window: Critical and High fixes requested by the customer are backported specifically to this version and delivered as patches or combo patches. This ensures that customers only deploy the specific fixes they are concerned with, avoiding unnecessary changes to their production environment.
Note: While we understand the constraints of regulated environments, Uxopian recommends the Monthly Stability Updates as the most virtuous approach. We encourage a "lazy-update" strategy where customers deploy monthly updates only when required—specifically when an update resolves a known issue impacting their operations.
Support Policy
Support windows are structured around the release of the next LTS version. Each LTS moves through two clearly defined phases:
1. Full Support An LTS remains in Full Support until one year after the subsequent LTS is released. Full Support includes all defect corrections, all security patches, and compatibility issue corrections, as long as they don’t introduce breaking changes.
2. Maintenance Support After the Full Support period, the LTS enters one year of Maintenance Support. Maintenance Support includes, in the limit of not putting customers at risk with breaking changes:
- Fixes for Critical and High CVEs
- Remediation of defects that severely block production operations
No functional evolution or minor defect corrections are provided during this phase. After the Maintenance period, the version reaches End of Life (EOL).