OpCon Release Schedule: What to Expect
At Continuous, we aim to provide a predictable, transparent release cadence that helps our customers plan, test, and adopt OpCon updates with confidence. This document explains how releases work, when to expect them, and what actions our customers should take.
Our Release Process
Each OpCon release follows a structured lifecycle designed to ensure quality, stability, and customer readiness:
-
Ideation: We gather ideas from customer feedback, partner input, and internal insights.
-
Refinement: Ideas are reviewed, scoped, prioritized, and scheduled into upcoming release windows
-
Publishing: Approved features are documented and communicated ahead of testing and release.
-
Work Window: Engineering builds, validates, and stabilizes features and fixes.
-
User Acceptance Testing (UAT): Approximately 2-3 weeks prior to production release, UAT is conducted to validate functionality and support overall release readiness.
While we follow this lifecycle consistently, timelines may adjust when necessary to address quality, security, or operational considerations.
Release Cadence Overview
Rather than fixed calendar dates, OpCon releases follow a quarter-based cadence, with production releases typically occurring in the second month of each quarter. This approach provides a consistent planning framework while allowing flexibility as needed.
| Release Type | Typical Timing |
|---|---|
| Q1 Release | 2nd month of Q1 |
| Q2 Release | 2nd month of Q2 |
| Q3 Release | 2nd month of Q3 |
| Q4 Release | 2nd month of Q4 |
Cloud-Hosted vs. Self-Hosted OpCon
Cloud-Hosted OpCon
-
Quarterly feature releases
-
New functionality delivered incrementally throughout the year
-
Ideal for customers who want faster access to innovation with minimal operational overhead
Self-Hosted
-
Annual feature release (equivalent to a long-term support release)
-
Quarterly maintenance releases focused on fixes and stability
-
Designed for customers who prefer controlled upgrade cycles
What This Means for You
OpCon’s release cadence is designed to help customers stay informed and plan adoption on their own timelines.
-
Ahead of a release window: Review published release notes and upcoming changes to understand potential impact to your environment
-
Leading up to production release: Be aware of upcoming updates and plan any internal readiness or communication as needed
-
After production release: Review delivered features and fixes to determine when and how to adopt new functionality
This cadence is designed to provide predictable delivery while allowing flexibility, so that our customers can adopt updates on their own timelines.
Frequently Asked Questions
Do I need to upgrade every quarter?
No. Customers can choose when to adopt feature releases within the 36-month support window.
Are maintenance releases required?
Maintenance releases are recommended for stability and fixes, especially for self-hosted environments.
Will release dates change?
Specific dates may adjust, but the quarterly cadence remains consistent.