Continuent has traditionally had a relaxed policy about the ongoing support and upgrade requirements for customers using our products, particularly our older releases and versions. We know that some customers prefer to use a version of the software that they are comfortable with and prefer to follow the ‘If it isn’t broken, don’t fix it’ approach.
While this has been fine for some time, Continuent are now working with and supporting versions of our product which are, in some cases, many years old. Since 2016, our policy is to regularly release new versions of our software on a more aggressive schedule than in the past, and this has led us to change our End-of-Life (EOL) policy for software.
Continuent release schedule
Continuent operates a continuous release schedule using the following basis:
- One major release version every 12 months (e.g. v6.x, v7.x)
- One minor (feature) release version every 3 months (e.g. v6.1, v6.2)
- One bug fix release every 6 weeks (e.g. v6.1.1)
While we may not always be able to achieve these dates, these are the milestones and targets we aim for.
Continuent End-of-Life policy
The standard Continuent EOL policy for all product versions is three (3) years from the release of the corresponding major (x-version) release.
The policy is used to ensure that we can continue to support our customers with the best and latest version of the software. Throughout the lifecycle of the product we endeavour to help you upgrade Continuent software to the latest version, and to provide you with the most efficient methods and tools to achieve that.
Because there is a new major version every year, it should be possible to upgrade the product easily. This provides a period of 3 years to upgrade to the next available major version.
Meanwhile, for a product that is within its support lifecycle, we provide the following:
- Full support for using and addressing, fixing problems with our software
- Bug fixes up until EOL is enacted
- All improvements to existing functionality applicable to the major release version up until the EOL is reached
- Upgrade assistance to keep your version up to date
Once a product reaches EOL:
- Upgrades, and assistance to upgrade to a supported version, will continue to be provided
- Improvements to existing features will no longer be available
- Bug fixes will no longer be available
- Support for that version will no longer be provided
Plan of action for Continuent customers
We appreciate that for existing customers the inception of this new policy may present a problem and uncertainty with the support and availability of the product, bug fixes, and assistance.
Because of this, we have agreed to a transitional arrangement for all of our existing customers and versions, which has a different policy based on the version. Releases earlier than v5.0.0 are treated differently than v5.x, which are treated differently from v6.0.0 and above.
The aim with this schedule is to encourage all users to upgrade to at least v5.3.x, while still providing support to customers that have upgraded to this major release until mid-2019. By this time, v7.0 will have been released.
- All releases v6.0.0 and greater follow the standard EOL policy schedule.
- All releases prior to v5.0.0 expired on April 17, 2017, but a 6-month grace period from the date of this announcement will apply for customers to upgrade to a later release. Therefore, if you currently use v4.0.2, we will provide assistance through until October 31, 2018 to get you upgraded to a v5.3.x or v6.x release.
- All versions in the v5.x sequence are exempt from our standard 3-year policy and are granted an 18-month expiry to match their respective release dates:
- v5.0 was released December 7, 2016, so the extended EOL expiration date is June 30, 2018.
- v5.1 was released April 26, 2017, so the extended EOL expiration date is October 26, 2018.
- v5.2 was released July 19, 2017, so the extended EOL expiration date is January 31, 2019.
- v5.3 was released December 12, 2017, so the extended EOL expiration date is June 7, 2019.
For releases and versions older than 5.0, we encourage all users to upgrade. In cases where we know that you are using an older version, we will be in touch to discuss your upgrade process and options.
If you are using an older version and have not yet been contacted by us, please do get in touch with Continuent sales or support. If you are using an older version and do not want to upgrade to a later version, please contact our sales team to discuss your options.
Where to find EOL information
We are committed to making the EOL policy and information about the product availability as transparent and open as possible. For our EOL policy as noted above, visit www.continuent.com/about/end-of-life-policy.
You can also find the exact date when a product release is set to go EOL in the release notes for that particular version. For example, view Tungsten Clustering 6.0 release notes.
If you have any further questions about our EOL policy, how it applies to you or how to upgrade, please contact our technical team via the support portal or our sales team.