OpenText | Support Lifecycle

[Dave Rabelink]

Find the release dates and subsequent sustaining maintenance for your OpenText products

Product Name	Version	Release Date	Sustaining
Gupta Team Developer (TD)	7.0	October 2016	October 2021
Gupta Team Developer (TD)	6.3	March 2015	March 2020
Gupta Team Developer (TD)	6.2	June 2013	August 2017
Gupta Team Developer (TD)	6.1	March 2012	March 2016
Gupta Team Developer (TD)	6.0	November 2010	March 2015
Gupta Report Builder	7.0	October 2016	October 2021
Gupta Report Builder	6.3	March 2015	March 2020
Gupta Report Builder	6.2	June 2013	August 2017
Gupta Report Builder	6.1	March 2012	March 2016
Gupta Report Builder	6.0	November 2010	March 2015
Gupta SQLBase	12.0	August 2015	August 2020
Gupta SQLBase	11.7	November 2012	November 2017
Gupta SQLBase	11.6	November 2010	September 2016
Gupta SQLBase	11.5	November 2008	August 2015
Gupta TD Mobile	2.1	February 2017	February 2022
Gupta TD Mobile	2.0	September 2015	September 2020
Gupta TD Mobile	1.2	January 2015	November 2016
Gupta TD Mobile	1.1	July 2014	November 2016
Gupta TD Mobile	1.0	January 2014	September 2015
Gupta Q	1.0.1	April 2010	April 2015

[Steve Leighton]

... but be wary of how OpenText define the term 'Sustaining' .

I recently had occasion to get tangled with TD6.2 which they state is 'Sustaining' until 'August 2017'.
but this is NOT the case !

Here is one of OpenText's explanation of 'Sustaining' as at 08 March 2017 ( confused ? you will be ) . Note the example relating to TD6.2 in particular:

In the 'pre-OpenText', Development produced patches, etc. for a product until two subsequent releases, i.e. Once 7.0 is released, the versions in Engineering Support (changes made and new releases) were then 7.0 and 6.3, but 6.2 was no longer maintained.
Technical Support was always available for as long as we could help out.
I'm not sure what the OT stance is on older products that were already out of Engineering Support when we came into their stable. The roadmap that you are looking at shows 'Sustaining'. The definition of Sustaining is:

"Sustaining Maintenance" refers to the stage of the product lifecylce following the expiration of current maintenance. During this phase of the product support lifecycle, the following support services *may be available:
Unlimited number of support request submissions
Access to the customer service portal (documentation, technical articles, discussion forums, webinars and events)
?* The terms and length of phases of the product support lifecycle may vary depending on the product and version. "
The definition of Current Maintenance is:
"When a new version of an OpenText product is released, it is considered to be under Current Maintenance for a period of 5 years from the version release date. Subject to any limitations described in the Handbook, which shall include Sections 2.4.5 and 4, products under Current Maintenance benefit from assigned R&D resources and offer the following features:
Unlimited number of support request submissions through the Customer Portal, Customer Self Service App, or traditional channels (i.e. telephone, email).
Service packs and / or patches.
The ability to request hot fixes.
The ability to report product defects.
The ability to request enhancements or new features.
Access to documentation online.
Access to technical articles and discussion forums in the Customer Portal.
Access to technical webinars and events.
Access to Global Service offerings (additional charge)."
So, 6.2 was released in 2013, which according to the Current Maintenance definitions would indicate that it's supported until 2018, but as I say, I don't know how (or if) that applies to products already released before we were acquired by OT. I suspect that their disclaimer about "The terms and length of phases of the product support lifecycle may vary depending on the product and version." would give them an out.
But in any case, there won't be any more TD6.2 releases.

[Dave Rabelink]

Thanks Steve for pointing this out.