EOL (end-of-life) Schedule - Revision history

Dgreenwood: /* What EOL Means */

2026-06-08T19:03:59Z

What EOL Means

← Older revision		Revision as of 14:03, 8 June 2026
Line 3:		Line 3:
	===What EOL Means===		===What EOL Means===

	You may continue using your existing Grooper installation and licensing.		* You may continue using your existing Grooper installation and licensing.
	You may still contact our support team with questions or issues related to an EOL version.		* You may still contact our support team with questions or issues related to an EOL version.
	While we will make every effort to assist users running EOL versions, we cannot guarantee issue resolution without upgrading to a supported version.		* While we will make every effort to assist users running EOL versions, we cannot guarantee issue resolution without upgrading to a supported version.
	We will no longer release patches, bug fixes, or feature updates for EOL versions.		* We will no longer release patches, bug fixes, or feature updates for EOL versions.

	===Why Upgrade?===		===Why Upgrade?===

Dgreenwood at 19:01, 8 June 2026

2026-06-08T19:01:35Z

← Older revision		Revision as of 14:01, 8 June 2026
Line 1:		Line 1:
	~~In order to improve~~ our platform and ~~provide our users with groundbreaking features~~, we ~~schedule "end~~-of-~~life" events~~ for each version of Grooper. ~~Just because~~ a version ~~is end-of-life (or~~ EOL) does not mean you ~~won't be able to user older versions of Grooper~~. ~~We simply will not be~~ actively ~~improving an EOL version~~.		To continue improving our platform and delivering innovative new capabilities, we establish an End-of-Life (EOL) date for each version of Grooper. When a version reaches EOL, it does not mean you can no longer use it. Rather, it means that version is no longer actively developed or maintained.

	~~Here's what that means:~~		===What EOL Means===
	* You will still be able to use your existing EOL ~~installation and licensing.~~
	* You will still be able to call into support with EOL version issues and questions
	* Although we will do our best to assist EOL version users experiencing issues, we cannot guarantee issue resolution without upgrading
	* We will not be issuing patches or updates to address bugs in EOL versions

			You may continue using your existing Grooper installation and licensing.
			You may still contact our support team with questions or issues related to an EOL version.
			While we will make every effort to assist users running EOL versions, we cannot guarantee issue resolution without upgrading to a supported version.
			We will no longer release patches, bug fixes, or feature updates for EOL versions.

	For users on an EOL version, we would strongly encourage you to think about updating to the most recent Grooper version. In addition to ensuring you will continue to receive regular updates, the new functionality we have introduced over the past few years will almost certainly improve and streamline your existing Grooper processes – and will probably enable you to use Grooper in new ways and achieve new efficiencies.		===Why Upgrade?===

	~~Although it is not a requirement~~, we ~~recommend that all users who decide~~ to upgrade ~~also engage an engineer from our professional services department~~. ~~All of our engineers have a high degree of skill~~ and ~~experience in assisting users~~ to ~~achieve~~ the ~~best results possible~~, and ~~will greatly expedite the upgrade process~~.		If you are currently using an EOL version, we strongly encourage you to upgrade to the latest release of Grooper. In addition to receiving ongoing updates and support, you'll gain access to new features and enhancements introduced over the past several years. These improvements can help streamline existing processes, increase efficiency, and unlock new ways to leverage Grooper across your organization.

	If you have any questions ~~or concerns~~ about the ~~end-of-life~~ process or upgrading, please ~~don’t hesitate to~~ contact your ~~client success~~ representative~~, your client fulfillment representative,~~ or our ~~support desk~~.		===Professional Services Recommendation===

			While not required, we recommend engaging a member of our Professional Services team when planning an upgrade. Our engineers have extensive experience helping customers successfully migrate to newer versions of Grooper and optimize their solutions. Their expertise can help minimize downtime, reduce risk, and accelerate the upgrade process.

			===Questions?===

			If you have any questions about the EOL process or upgrading to a newer version of Grooper, please contact your Client Success representative or our Support team. We are happy to help you evaluate your options and plan your next steps.

	==EOL Schedule==		==EOL Schedule==

Dgreenwood: /* EOL Versions */

2026-06-08T18:53:15Z

EOL Versions

← Older revision		Revision as of 13:53, 8 June 2026
Line 33:		Line 33:
	{\|class="wikitable"		{\|class="wikitable"
	\|'''Version'''\|\|'''Release Date'''\|\|'''EOL Date'''\|\|'''Lifespan'''		\|'''Version'''\|\|'''Release Date'''\|\|'''EOL Date'''\|\|'''Lifespan'''
			\|-
			\|2023\|\|Mar 16, 2023\|\|Mar, 16 2026\|\|36mo
	\|-		\|-
	\|2022\|\|Jul 12, 2022\|\|Jan 17, 2025\|\|30mo		\|2022\|\|Jul 12, 2022\|\|Jan 17, 2025\|\|30mo

Dgreenwood: /* Current Versions */

2026-06-08T18:53:03Z

Current Versions

← Older revision		Revision as of 13:53, 8 June 2026
Line 28:		Line 28:
	\|-		\|-
	\|2023.1\|\|Dec 28, 2023\|\|Dec 28, 2026\|\|36mo		\|2023.1\|\|Dec 28, 2023\|\|Dec 28, 2026\|\|36mo
	\|-
	~~\|2023\|\|Mar 16, 2023\|\|Mar, 16 2026\|\|36mo~~
	\|}		\|}

Dgreenwood: /* Current Versions */

2025-06-30T19:38:27Z

Current Versions

← Older revision		Revision as of 14:38, 30 June 2025
Line 22:		Line 22:
	{\|class="wikitable"		{\|class="wikitable"
	\|'''Version'''\|\|'''Release Date'''\|\|'''EOL Date'''\|\|'''Lifespan'''		\|'''Version'''\|\|'''Release Date'''\|\|'''EOL Date'''\|\|'''Lifespan'''
			\|-
			\|2025\|\|Apr 2, 2025\|\|Apr 2, 2028\|\|36mo
	\|-		\|-
	\|2024\|\|Sep 4, 2024\|\|Sep 4, 2027\|\|36mo		\|2024\|\|Sep 4, 2024\|\|Sep 4, 2027\|\|36mo

Dgreenwood: /* EOL Versions */

2025-01-28T17:26:15Z

EOL Versions

← Older revision		Revision as of 12:26, 28 January 2025
Line 33:		Line 33:
	{\|class="wikitable"		{\|class="wikitable"
	\|'''Version'''\|\|'''Release Date'''\|\|'''EOL Date'''\|\|'''Lifespan'''		\|'''Version'''\|\|'''Release Date'''\|\|'''EOL Date'''\|\|'''Lifespan'''
			\|-
			\|2022\|\|Jul 12, 2022\|\|Jan 17, 2025\|\|30mo
			\|-
			\|2021\|\|Aug 30, 2021\|\|Jan 17, 2025\|\|42mo
	\|-		\|-
	\|2.90\|\|July 28, 2020\|\|April 28, 2023\|\|33mo		\|2.90\|\|July 28, 2020\|\|April 28, 2023\|\|33mo

Dgreenwood: /* Current Versions */

2025-01-28T17:25:47Z

Current Versions

← Older revision		Revision as of 12:25, 28 January 2025
Line 28:		Line 28:
	\|-		\|-
	\|2023\|\|Mar 16, 2023\|\|Mar, 16 2026\|\|36mo		\|2023\|\|Mar 16, 2023\|\|Mar, 16 2026\|\|36mo
	\|-
	~~\|2022\|\|Jul 12, 2022\|\|Jan 17, 2025\|\|30mo~~
	\|-
	~~\|2021\|\|Aug 30, 2021\|\|Jan 17, 2025\|\|42mo~~
	\|}		\|}

Dgreenwood: /* Current Versions */

2024-09-30T20:40:09Z

Current Versions

← Older revision		Revision as of 15:40, 30 September 2024
Line 22:		Line 22:
	{\|class="wikitable"		{\|class="wikitable"
	\|'''Version'''\|\|'''Release Date'''\|\|'''EOL Date'''\|\|'''Lifespan'''		\|'''Version'''\|\|'''Release Date'''\|\|'''EOL Date'''\|\|'''Lifespan'''
			\|-
			\|2024\|\|Sep 4, 2024\|\|Sep 4, 2027\|\|36mo
	\|-		\|-
	\|2023.1\|\|Dec 28, 2023\|\|Dec 28, 2026\|\|36mo		\|2023.1\|\|Dec 28, 2023\|\|Dec 28, 2026\|\|36mo

Dgreenwood: /* Current Versions */

2024-01-04T15:45:38Z

Current Versions

← Older revision		Revision as of 10:45, 4 January 2024
Line 22:		Line 22:
	{\|class="wikitable"		{\|class="wikitable"
	\|'''Version'''\|\|'''Release Date'''\|\|'''EOL Date'''\|\|'''Lifespan'''		\|'''Version'''\|\|'''Release Date'''\|\|'''EOL Date'''\|\|'''Lifespan'''
			\|-
			\|2023.1\|\|Dec 28, 2023\|\|Dec 28, 2026\|\|36mo
	\|-		\|-
	\|2023\|\|Mar 16, 2023\|\|Mar, 16 2026\|\|36mo		\|2023\|\|Mar 16, 2023\|\|Mar, 16 2026\|\|36mo

Dgreenwood at 14:49, 19 December 2023

2023-12-19T14:49:36Z

← Older revision		Revision as of 09:49, 19 December 2023
Line 10:		Line 10:
	For users on an EOL version, we would strongly encourage you to think about updating to the most recent Grooper version. In addition to ensuring you will continue to receive regular updates, the new functionality we have introduced over the past few years will almost certainly improve and streamline your existing Grooper processes – and will probably enable you to use Grooper in new ways and achieve new efficiencies.		For users on an EOL version, we would strongly encourage you to think about updating to the most recent Grooper version. In addition to ensuring you will continue to receive regular updates, the new functionality we have introduced over the past few years will almost certainly improve and streamline your existing Grooper processes – and will probably enable you to use Grooper in new ways and achieve new efficiencies.

	Although it is not a requirement, we recommend that all users who decide to upgrade also engage an engineer from our ~~client fulfillment~~ department. All of our engineers have a high degree of skill and experience in assisting users to achieve the best results possible, and will greatly expedite the upgrade process.		Although it is not a requirement, we recommend that all users who decide to upgrade also engage an engineer from our professional services department. All of our engineers have a high degree of skill and experience in assisting users to achieve the best results possible, and will greatly expedite the upgrade process.

	If you have any questions or concerns about the end-of-life process or upgrading, please don’t hesitate to contact your client success representative, your client fulfillment representative, or our support desk.		If you have any questions or concerns about the end-of-life process or upgrading, please don’t hesitate to contact your client success representative, your client fulfillment representative, or our support desk.