Release Schedule
This page outlines the planned release schedule for the product, including major, minor, and patch releases. The goal is to provide transparency on upcoming updates, maintenance phases, and upgrade recommendations to help users plan accordingly.
Release Cadence
New major versions of the product release approximately every 4-8 months, introducing significant features, architectural changes, and potential breaking updates. Minor releases occur more frequently to add enhancements and optimizations, while patch releases issue as needed for bug fixes and security improvements.
Active projects are strongly recommended to upgrade to the latest major version as soon as possible after its general availability to benefit from new capabilities and ensure ongoing support.
Major Versions and Maintenance
This section outlines the lifecycle of major.minor versions (e.g., 1.0 or 2.5) releases. Each version follows a structured maintenance schedule to ensure reliability, security, and support for users.
Maintenance Phases Explained
General Availability (GA): The initial release date when the version becomes publicly available and enters the support lifecycle.
Mainstream Maintenance: Upon GA release, Mainstream Maintenance begins and typically includes:
- Patches and Enhancements: Customers receive regular updates, bug fixes, and security patches to keep the software relevant and efficient.
- Technical Support: Customers receive assistance troubleshooting issues, implementing updates, and optimizing systems.
- Compatibility and Integration: Mainstream Maintenance ensures the product remains compatible with other systems and technologies businesses use.
Extended Maintenance: Customers can extend the support period for an increased maintenance fee to address corrections or legal changes. Extended Maintenance serves customers needing additional time to transition to newer major versions or adapt their business processes before making significant upgrades. This period ensures continued support, albeit with some limitations and higher costs than Mainstream Maintenance. In this phase, customer support typically includes:
- Continued Support and Issue Resolution: Customers receive support for critical issues and major bugs that might disrupt business operations. While not as comprehensive as Mainstream Maintenance, support covers significant problems affecting the stability and security of the software.
- Security Patches: Customers receive essential security patches to protect against vulnerabilities and threats. These patches prove critical in maintaining customer data and system integrity as the software ages.
- Technical Support: Support remains available but might have certain restrictions or prioritization differences. Support services during this phase help businesses maintain operational continuity and address significant issues.
- No New Features or Enhancements: Extended Maintenance does not include introducing new features, functionalities, or enhancement packages. The focus centers on maintaining the existing system rather than evolving it with new capabilities.
- Higher Costs: Extended Maintenance costs typically exceed Mainstream Maintenance fees. This premium reflects the additional effort needed to support older software. Businesses need to weigh these costs against the benefits of upgrading to newer major versions.
- Migration Planning and Support: Guidance and support for planning migrations to newer major versions. This includes providing tools and resources to help with the transition process.
End-of-Life (EOL): Occurs after Extended Maintenance. No further updates, fixes, or support are available.
Version Timeline
The table below summarizes key dates for each major.minor version:
| Version | General Availability | End of Mainstream Maintenance | End of Extended Maintenance |
|---|---|---|---|
| 1.0.0 | January 2025 | December 2025 | December 2025 |
| 2.0.0 | July 2025 | December 2025 | December 2025 |
| 2.5.0 | October 2025 | December 2026 | December 2026 |
WARNING
Patch releases (e.g., 1.0.1 or 2.5.1) follow the same maintenance schedule as their parent major.minor version (e.g., 1.0 or 2.5). They include only backward-compatible changes to ensure seamless upgrades.
Releases may be adjusted based on development needs and feedback. For historical details, refer to the Release Notes.