Synergy/DE Release Strategy
The table below shows end-of-support dates for all Synergy/DE versions.
|Synergy/DE Version||Release Date||End-of-Support Date|
|12/16/2022 OpenVMS Alpha & I64
11/17/2022 Windows, IBM AIX, Linux
|The date of the next feature release or LTS release—plus three months|
LTS (Long-Term Support) Release
|4/1/2022||April 1, 2026 (four years after its release date)
one year after the next LTS version is released
—whichever is later
|11.1||9/30/2019||9/30/2023 (four years after its release date)|
|Lower than 11.1||N/A||Retired|
Critical fixes (for production-down issues) and urgent security updates will be provided for each Synergy/DE version until its end-of-support date. Other fixes will be provided in LTS updates and subsequent feature releases.
We recommend you stay current with your Synergy/DE version, and with updates to your version, to keep your system secure and performing well. Synergex’s Developer Support team will try to assist you with any Synergy/DE version, but their ability to help with versions past their end-of-support date may be limited.
For Synergy DBL Integration for Visual Studio (SDI), only the current build is supported. Each subsequent SDI build immediately replaces the previous build as the supported version.
Synergy/DE’s runtime version targeting enables you to use the latest feature-release and SDI tools while deploying to an LTS release or feature release production platform.
Long-Term Support (LTS) Releases
Our release strategy for Synergy/DE products combines long-term support (LTS) releases with feature releases. LTS releases provide a stable platform that’s supported for an extended period of time, with only quality, security, and platform updates—no new features. The primary characteristics of an LTS release are
- A two-year release cadence, allowing you to plan your own updates accordingly
- A four-year minimum support period (or one year after the next LTS release ships, whichever is longer)
- Limited changes to the code base
Because Synergy has close ties with Microsoft .NET, we’ve broadly aligned our release schedule with the .NET release schedule, which also uses an LTS strategy and a two-year cadence. Version numbers for LTS releases have an odd major revision number, for example, 12.1.
Feature releases deliver the latest technologies and enhancements, which build consecutively to the next LTS release. The primary characteristics of a feature release are
- Access to new features and enhancements as soon as they’re completed
- A more frequent release cadence
- A shorter period of support (three months after a subsequent feature or LTS release)
While feature releases are fully tested, quality may be lower in areas where new code has been added or significant changes have been made. Quality will solidify as developers exercise the new features and our automated test suites are extended. Version numbers for feature releases have an even major revision number, for example, 13.2. Fixes to a feature release will only be provided via the next feature (or LTS) release.