From f4e67d0a9ceffe4b5535170d90109f122a0c9a97 Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Wed, 22 Jan 2025 11:25:26 +0100 Subject: [PATCH 1/2] Fast Track info removed, LTS derscription added --- docs/resources/release_process_and_roadmap.md | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/docs/resources/release_process_and_roadmap.md b/docs/resources/release_process_and_roadmap.md index 6fcda0bb80..d28963ea71 100644 --- a/docs/resources/release_process_and_roadmap.md +++ b/docs/resources/release_process_and_roadmap.md @@ -17,12 +17,23 @@ Additionally, [[= product_name =]] also has an open-source version called [[= pr The [[= product_name_oss =]] code is available on GitHub under the GPLv2 license. It comes with no commercial support and maintenance services. -[[= product_name_base =]] manages the release of [[= product_name =]] by using an agile iterative process and a continuous software development model, which is why we provide two kinds of [[= product_name =]] releases: +[[= product_name_base =]] manages the release of [[= product_name =]] by using an agile iterative process and a continuous software development model, which is why we provide Long Term Support releases (LTS) of [[= product_name =]] releases. -- Long Term Support releases (LTS) which are supported by [[= product_name_base =]] for a long period of time. -- Fast Track releases (FT) give access to the latest features and are supported for a short period of time. They're maintained only until the next FT release is introduced. +Long Term Support releases (LTS) are supported by [[= product_name_base =]] for a long period of time. +They're suitable for highly stable enterprise rollouts. -FT releases are tailored for those who want to stay up-to-date with newest functionalities, while LTS releases are suitable for highly stable enterprise rollouts. +LTS releases provide you with: + +- **Reliability and stability**, as they go through extensive testing to ensure they are free from major bugs and issues. +- **Long-term security**, as a result of updates and security patches. +- **Predictability** that comes from following an established release plan. +- **Reduced maintenance**, because you avoid the frequent upgrade cycles. + +With LTS Updates customers can maintain their competitiveness by incorporating cutting-edge technologies into their LTS releases without losing stability. +LTS Updates are intended to improve the current platform by providing new features. +What's important, you are not required to switch to a newer version of [[= product_name =]] to use LTS Updates. +You can install them whenever you choose, and you can be sure that the next LTS release will include them by default. +You won't have to manually install or configure them after upgrading, so you can make the switch over smoothly when the time comes. ## Versioning conventions From b588b4b54a25e91c5270c2b06506333f55888876 Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Mon, 3 Feb 2025 09:52:17 +0100 Subject: [PATCH 2/2] small fix --- docs/resources/release_process_and_roadmap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/resources/release_process_and_roadmap.md b/docs/resources/release_process_and_roadmap.md index d28963ea71..9d3577e982 100644 --- a/docs/resources/release_process_and_roadmap.md +++ b/docs/resources/release_process_and_roadmap.md @@ -33,7 +33,7 @@ With LTS Updates customers can maintain their competitiveness by incorporating c LTS Updates are intended to improve the current platform by providing new features. What's important, you are not required to switch to a newer version of [[= product_name =]] to use LTS Updates. You can install them whenever you choose, and you can be sure that the next LTS release will include them by default. -You won't have to manually install or configure them after upgrading, so you can make the switch over smoothly when the time comes. +You won't have to manually install or configure them after upgrading, so you can make the switch smoothly when the time comes. ## Versioning conventions