From e4398cd62e2426a4d94d4d2c059ba3b5f313aa89 Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Wed, 28 Aug 2024 13:51:21 +0530 Subject: [PATCH 01/11] created and add content to the new supported version page Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 141 ++++++++++++++++++++++++++++++++++ content/versions.md | 54 +++++-------- 2 files changed, 159 insertions(+), 36 deletions(-) create mode 100644 content/supported_versions.md diff --git a/content/supported_versions.md b/content/supported_versions.md new file mode 100644 index 0000000000..8403f12b15 --- /dev/null +++ b/content/supported_versions.md @@ -0,0 +1,141 @@ ++++ +title = "Supported Versions(LTS/Innovation)" +draft = false +gh_repo = "chef-web-docs" +aliases = ["/versions.html"] +product = ["automate", "client", "server", "habitat", "inspec", "supermarket", "workstation"] + +[menu] + [menu.overview] + title = "Supported Versions(LTS/Innovation)" + identifier = "overview/packages_&_platforms/supported_versions.md Supported Versions(LTS/Innovation)" + parent = "overview/packages_&_platforms" + weight = 35 ++++ + +This section lists the free and commercial On-Premises Chef products and versions we support based on our new Long-term support policy. This policy, which defines Chef Software's involvement in updating and maintaining each product, has significant implications for our customers and their products. + +## Product Releases + +Progress Chef runs different releases that can run in parallel, and our customers can adapt them based on their needs. Following are releases chef supports: + +### Innovation (I) Release + +- Innovation releases are designed for customers seeking faster modernization and innovation. Progress recommends using continuous integration and continuous delivery to help benefit from the more rapid release cadence. Innovation releases also allow all customers to explore features appearing in future LTS releases. +- With the introduction of LTS in Chef, any other major release will be termed an Innovation Release. This release will not be time-bound and will allow Progress Chef to release significant versions and new features without LTS. + +### Long-Term Supported (LTS) Release + +- From time to time, Progress may elect to designate a new release as Long Term Supported (LTS). Customers who primarily look for stability and minimal change for their implementation over many years can adapt to the LTS release. +- The software will get support depending on the timeline decided with LTS. +- Upgrade planning is more manageable for customers since they know when the next LTS version will be out. + +### Non-Supported (NS) Releases – Technical/Private Preview/Alpha/Beta Release + +- Progress may offer Technical/Private Previews containing Technical Preview Features on a Progress-hosted environment under the terms in the applicable End User License Agreement. +- Progress may preview Features/Products planned to be released as future LTS features/products so that customers can validate if new features/products meet their use case and provide early feedback to Progress ahead of a general release. +- This release does not include CVE fixes, which Progress may choose to do. +- For Chef products, customers must move to GA release once GA is available. We do not provide any support for any release candidates such as Alpha Beta or Private Preview post the GA launch + +### Lifecycle Definitions + +- Each Innovation and LTS release has its own lifecycle starting at GA, migrates, and ends as described below: + +### Generally Available (GA) + +This stage indicates that the product or version is actively developing and maintaining. + +- GA releases are fully supported (LTS or Innovation). If you face any problems, Progress will work with you to find an appropriate resolution if active maintenance and support services cover them. +- Chef continues to provide releases to the application or version in response to customer needs and security vulnerabilities. +- Chef welcomes customer feature requests for the product roadmap for the application. +- Progress will evaluate GA releases for certifications of new third-party products, including new operating system versions. When porting to new operating systems that were not previously supported, only LTS versions will be considered. + +### Migration Phase (MP) + +- An LTS/I release enters the Migration Phase with the launch of the LTS+/I+ release. When the Sunset Phase starts, in parallel, the Migration Phase starts, which is the transition period provided to customers to move to LTS+/I+. +- LTS and Innovation releases in the Migration Phase are fully supported. Progress will evaluate them for certifications on new operating environments but not for ports to new hardware systems. +- If you face any problem using product releases in the Migration Phase, Progress will work with customers toward an appropriate resolution where possible if active maintenance and support services cover their licenses. + +### Sunset Phase (Only for LTS releases) + +- After fulfilling the following conditions, an LTS release enters the Sunset Phase. +- When the launch of the release is for two or more years, and +- A new LTS version has been released. +- The Sunset phase does not apply to Innovation releases. Once a subsequent Innovation release becomes available, the prior Innovation release immediately moves to the EOL life cycle phase with a given period of migration phase. +- If you face any problem using product releases in the Sunset Phase, Progress will work with customers towards an appropriate resolution where possible if active maintenance and support services cover their licenses. The resolution includes the possibility of an Update provided by Progress. We are committed to providing continuous support even during the Sunset Phase, ensuring your confidence in our products. +- Progress does not provide standard support for the LTS release in the Sunset Phase unless the customer has opted for Extended Paid Support. Progress recommends that customers plan to upgrade from Sunset Phase product releases using this document as a guideline. + +### End Of Life (EOL) Phase + +The following describes the general impact of a product reaching EOL. For more details, refer to the official EOL communication, usually delivered via email. You can also find this information [here]. + +- This stage indicates that Progress has set a date after which the application or version will no longer be supported or recommended for customers' use. +- Products covered by active maintenance and support services at the time of an announced EOL will continue receiving Technical Support on the same terms as Sunset product releases for the duration of the purchased maintenance and support services. +- Progress does not allow renewal of maintenance and support services for EOL products. +- Once the existing maintenance and support services expire, Progress will not provide any further enhancements or fixes or entertain any new support cases. The existing product documentation, knowledgebase articles, and online user community discussions will remain the only support. +For more details on the Chef on Prem Life Cycle Policy, click here + +### Versions and Status + +Progress Chef has transitioned from N-1 and N-2 Support Policy to LTS++ and I++ Support Strategy. The Support strategy works like follows: + +- LTS for Progress Chef will be for three years. +- LTS will follow the released version. + - For Example, Chef Infra 19 LTS is a significant version. All minor releases are like 19. X and patches are like 19.2.x and will fall under LTS support. +- As the Product EOL date is predetermined, a new release is not required to publish this message. +- There can be more than one Innovation release between the next LTS release. For example, Chef Infra 20 and 22 will be an Innovation Release, and the next LTS release can be Chef 23 LTS. +- When LTS is released, it will have a declared sunset date that is not to be shorter than two years. The LTS will only be marked ‘Sunset’ when the date (>=2 yr) has elapsed and a new LTS version is released. 'Sunset' in this context means the end of active support and the start of the EOL phase. +- Customers will then have a specified migration time (no less than 6 months) declared as part of the LTS+ release. At the end of the “migration window,” LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress). +- Upon releasing I+, the current Innovation release is EOL and subject to the migration window. + +## Supported Commercial Distributions + +Use of these and later versions of these distributions must be by the Chef End User License Agreement or a commercial agreement with the Chef. Additional information is available in this announcement. + +| Product | Version | Release | Lifecycle Status | Release Date | EOL Date | +|-------------------|---------|---------|------------------|--------------|---------------------------------------| +| Chef Courier | 1.0 | I | GA | | 6 months after the release of I+ | +| Chef 360 Platform | 1.0 | I | GA | | 6 months after the release of I+ | +| Chef Infra Client | 19 | LTS | GA | | 3 years or more from the release date | +| Chef InSpec | 7 | LTS | GA | | 3 years or more from the release date | + +{{< note >}} Chef Backend does not directly require acceptance of the Chef EULA, but it does have functionality that requires its acceptance in other products. {{< /note >}} + +## Supported Free Distributions < to be updated by Eng.> + +Use of the following distributions is governed by the Apache License, version 2.0. + +| Product | Version | Lifecycle Status | EOL Date | +|-------------|---------|------------------|----------| +| Supermarket | 5.x | GA | TBD | + +## Deprecated products and versions + +The following products are deprecated, so move to newer versions or products. + +| Product | Version | Lifecycle Status | EOL Date | +|-------------------|---------|------------------|----------| +| Chef Infra Client | 18.x | TBD | TBD | +| Chef InSpec | 6.x | TBD | TBD | + +## End of Life (EOL) Products < this list should remain the same and must be maintained in the future according to new policy> + +| Product | Version | Lifecycle Status | EOL Date | +|--------------------------|---------------------|------------------|-------------------| +| Analytics | All | EOL | December 31, 2018 | +| Chef Automate | 1.x | EOL | December 31, 2019 | +| Chef Infra Client | 16 and under | EOL | November 30, 2022 | +| Chef Compliance Server | All | EOL | December 31, 2018 | +| ChefDK | All | EOL | December 31, 2020 | +| Chef Infra Server | 13.x | EOL | June 30, 2021 | +| Chef InSpec | 2 and under | EOL | December 31, 2019 | +| Chef InSpec | 3.x | EOL | April 30, 2020 | +| Chef InSpec | 4.x | EOL | November 14, 2023 | +| Chef Provisioning | All | EOL | August 31, 2019 | +| Chef Push Jobs | All | EOL | December 31, 2020 | +| Chef Replication/Sync | All | EOL | August 31, 2019 | +| Chef Server DRBD HA | All | EOL | March 31, 2019 | +| Chef Workflow (Delivery) | All | EOL | December 31, 2020 | +| Chef Workstation | 20.12.205 and under | EOL | December 31, 2021 | +| Enterprise Chef | All | EOL | December 31, 2018 | +| Reporting | All | EOL | December 31, 2018 | diff --git a/content/versions.md b/content/versions.md index 93c8b31d80..e0937a62b2 100644 --- a/content/versions.md +++ b/content/versions.md @@ -1,5 +1,5 @@ +++ -title = "Supported Versions" +title = "Supported Versions(till 2024)" draft = false gh_repo = "chef-web-docs" aliases = ["/versions.html"] @@ -7,42 +7,34 @@ product = ["automate", "client", "server", "habitat", "inspec", "supermarket", " [menu] [menu.overview] - title = "Supported Versions" - identifier = "overview/packages_&_platforms/versions.md Supported Versions" + title = "Supported Versions(till 2024)" + identifier = "overview/packages_&_platforms/versions.md Supported Versions(till 2024)" parent = "overview/packages_&_platforms" weight = 30 +++ -This section lists the free and commercial Chef products and versions we -currently support. The lifecycle stage defines the involvement by Chef -Software in updating and maintaining each product. +This section lists the free and commercial Chef products and versions we currently support and will continue to support until the end of year 2024 or till Infra Client 18 is End of Life (which ever happens first). The lifecycle stage defines the involvement by Chef Software in updating and maintaining each product. ## Lifecycle Definitions ### Generally Available (GA) -This stage indicates that the product or version is in active -development and/or maintenance. +This stage indicates that the product or version is in active development and/or maintenance. -- Chef continues to provide releases to the application or version in response to customer needs and security vulnerabilities -- Chef welcomes customer feature requests for the product roadmap for the application +- Chef continues to provide releases to the application or version in response to customer needs and security vulnerabilities. +- Chef welcomes customer feature requests for the product roadmap for the application. ### Deprecated -This stage indicates that an application or version is no longer in -active development and will eventually move to end of life status. Chef -continues to provide support [according to our -SLAs](https://www.chef.io/service-level-agreement/). +This stage indicates that an application or version is no longer in active development and will eventually move to end of life status. Chef continues to provide support [according to our SLAs](https://www.chef.io/service-level-agreement/). -- Chef no longer provides scheduled releases -- Customers should use the GA alternative to these products; contact us for help with product selection and deployment -- Chef may provide a release for a critical defect or security vulnerability +- Chef no longer provides scheduled releases. +- Customers should use the GA alternative to these products; contact us for help with product selection and deployment. +- Chef may provide a release for a critical defect or security vulnerability. ### End of Life (EOL) -This stage indicates that Chef has set a date after which the -application or version will no longer be supported or recommended for -use by customers. +This stage indicates that Chef has set a date after which the application or version will no longer be supported or recommended for use by customers. ### Versions and Status @@ -52,15 +44,13 @@ Chef Infra Client generally follows an N-1 support strategy. This means that if Unless otherwise stated, versions older than those listed below are EOL. +Chef Infra Client 19 and other chef products that will launch after Infra client 19 will follow new long term support policy. Please refer our new page for for more details. + {{< /important >}} ## Supported Commercial Distributions -Use of these and later versions of these distributions must be in -accordance with the [Chef End User License -Agreement](https://www.chef.io/end-user-license-agreement) or a -commercial agreement with Chef. Additional information is available in -[this announcement](https://www.chef.io/blog/chef-software-announces-the-enterprise-automation-stack). +Use of these and later versions of these distributions must be in accordance with the [Chef End User License Agreement](https://www.chef.io/end-user-license-agreement) or a commercial agreement with Chef. Additional information is available in [this announcement](https://www.chef.io/blog/chef-software-announces-the-enterprise-automation-stack). | Product | Version | Lifecycle Status | EOL Date | |-------------------|--------------------------|------------------|----------------| @@ -71,18 +61,11 @@ commercial agreement with Chef. Additional information is available in | Chef InSpec | 6.x | GA | n/a | | Chef Workstation | 22.x (2022), 23.x (2023) | GA | n/a | -{{< note >}} - -**Chef Backend** does not directly require acceptance of the Chef -EULA, but it does have functionality that requires its acceptance in other -products. - -{{< /note >}} +{{< note >}} **Chef Backend** does not directly require acceptance of the Chef EULA, but it does have functionality that requires its acceptance in other products. {{< /note >}} ## Supported Free Distributions -Use of the following distributions is governed by the Apache License, -version 2.0. +Use of the following distributions is governed by the Apache License, version 2.0. | Product | Version | Lifecycle Status | EOL Date | |-------------|---------|------------------|----------| @@ -90,8 +73,7 @@ version 2.0. ## Deprecated Products and Versions -The following products are deprecated. Users are advised to move to -newer versions or products. +The following products are deprecated. Users are advised to move to newer versions or products. | Product | Version | Lifecycle Status | EOL Date | |-------------------|---------|------------------|-------------------| From e87d45d206b8f6a8d3117e1a49a91e3229858f69 Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Wed, 28 Aug 2024 14:40:06 +0530 Subject: [PATCH 02/11] changes updated Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 22 +++++++++++----------- content/versions.md | 2 +- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/content/supported_versions.md b/content/supported_versions.md index 8403f12b15..3889f1e0eb 100644 --- a/content/supported_versions.md +++ b/content/supported_versions.md @@ -22,11 +22,11 @@ Progress Chef runs different releases that can run in parallel, and our customer ### Innovation (I) Release - Innovation releases are designed for customers seeking faster modernization and innovation. Progress recommends using continuous integration and continuous delivery to help benefit from the more rapid release cadence. Innovation releases also allow all customers to explore features appearing in future LTS releases. -- With the introduction of LTS in Chef, any other major release will be termed an Innovation Release. This release will not be time-bound and will allow Progress Chef to release significant versions and new features without LTS. +- With the introduction of LTS in Chef, any other major release will be termed an Innovation Release. This release will be flexible and allow Progress Chef to release significant versions and new features without LTS. ### Long-Term Supported (LTS) Release -- From time to time, Progress may elect to designate a new release as Long Term Supported (LTS). Customers who primarily look for stability and minimal change for their implementation over many years can adapt to the LTS release. +- From time to time, Progress may elect to designate a new release as Long-Term Supported (LTS). Customers who primarily look for stability and minimal change for their implementation over many years can adapt to the LTS release. - The software will get support depending on the timeline decided with LTS. - Upgrade planning is more manageable for customers since they know when the next LTS version will be out. @@ -35,11 +35,11 @@ Progress Chef runs different releases that can run in parallel, and our customer - Progress may offer Technical/Private Previews containing Technical Preview Features on a Progress-hosted environment under the terms in the applicable End User License Agreement. - Progress may preview Features/Products planned to be released as future LTS features/products so that customers can validate if new features/products meet their use case and provide early feedback to Progress ahead of a general release. - This release does not include CVE fixes, which Progress may choose to do. -- For Chef products, customers must move to GA release once GA is available. We do not provide any support for any release candidates such as Alpha Beta or Private Preview post the GA launch +- Customers must move to GA release once GA is available for Chef products. We do not provide any support for any release candidates such as Alpha Beta or Private Preview post the GA launch. ### Lifecycle Definitions -- Each Innovation and LTS release has its own lifecycle starting at GA, migrates, and ends as described below: +- Each Innovation and LTS release has its lifecycle starting at GA, migrates, and ends as described below: ### Generally Available (GA) @@ -48,13 +48,13 @@ This stage indicates that the product or version is actively developing and main - GA releases are fully supported (LTS or Innovation). If you face any problems, Progress will work with you to find an appropriate resolution if active maintenance and support services cover them. - Chef continues to provide releases to the application or version in response to customer needs and security vulnerabilities. - Chef welcomes customer feature requests for the product roadmap for the application. -- Progress will evaluate GA releases for certifications of new third-party products, including new operating system versions. When porting to new operating systems that were not previously supported, only LTS versions will be considered. +- Progress will evaluate GA releases for certifications of new third-party products, including new operating system versions. If you are porting to a new operating system that has not previously been supported, the LTS versions will be considered. ### Migration Phase (MP) - An LTS/I release enters the Migration Phase with the launch of the LTS+/I+ release. When the Sunset Phase starts, in parallel, the Migration Phase starts, which is the transition period provided to customers to move to LTS+/I+. - LTS and Innovation releases in the Migration Phase are fully supported. Progress will evaluate them for certifications on new operating environments but not for ports to new hardware systems. -- If you face any problem using product releases in the Migration Phase, Progress will work with customers toward an appropriate resolution where possible if active maintenance and support services cover their licenses. +- If you encounter any problems using product releases in the Migration Phase, Progress will work with customers toward an appropriate resolution where possible if active maintenance and support services cover their licenses. ### Sunset Phase (Only for LTS releases) @@ -62,12 +62,12 @@ This stage indicates that the product or version is actively developing and main - When the launch of the release is for two or more years, and - A new LTS version has been released. - The Sunset phase does not apply to Innovation releases. Once a subsequent Innovation release becomes available, the prior Innovation release immediately moves to the EOL life cycle phase with a given period of migration phase. -- If you face any problem using product releases in the Sunset Phase, Progress will work with customers towards an appropriate resolution where possible if active maintenance and support services cover their licenses. The resolution includes the possibility of an Update provided by Progress. We are committed to providing continuous support even during the Sunset Phase, ensuring your confidence in our products. -- Progress does not provide standard support for the LTS release in the Sunset Phase unless the customer has opted for Extended Paid Support. Progress recommends that customers plan to upgrade from Sunset Phase product releases using this document as a guideline. +- If you face any problem using product releases in the Sunset Phase, Progress will work with customers towards an appropriate resolution where possible if active maintenance and support services cover their licenses. The resolution includes the possibility of an Update provided by Progress. We are committed to continuous support even during the Sunset Phase, ensuring your confidence in our products. +- Progress only provides standard support for the LTS release in the Sunset Phase if the customer has opted for Extended Paid Support. Progress recommends that customers plan to upgrade from Sunset Phase product releases using this document as a guideline. ### End Of Life (EOL) Phase -The following describes the general impact of a product reaching EOL. For more details, refer to the official EOL communication, usually delivered via email. You can also find this information [here]. +The following describes the general impact of a product reaching EOL. For more details, refer to the official EOL communication, usually emailing. You can also find this information [here]. - This stage indicates that Progress has set a date after which the application or version will no longer be supported or recommended for customers' use. - Products covered by active maintenance and support services at the time of an announced EOL will continue receiving Technical Support on the same terms as Sunset product releases for the duration of the purchased maintenance and support services. @@ -84,8 +84,8 @@ Progress Chef has transitioned from N-1 and N-2 Support Policy to LTS++ and I++ - For Example, Chef Infra 19 LTS is a significant version. All minor releases are like 19. X and patches are like 19.2.x and will fall under LTS support. - As the Product EOL date is predetermined, a new release is not required to publish this message. - There can be more than one Innovation release between the next LTS release. For example, Chef Infra 20 and 22 will be an Innovation Release, and the next LTS release can be Chef 23 LTS. -- When LTS is released, it will have a declared sunset date that is not to be shorter than two years. The LTS will only be marked ‘Sunset’ when the date (>=2 yr) has elapsed and a new LTS version is released. 'Sunset' in this context means the end of active support and the start of the EOL phase. -- Customers will then have a specified migration time (no less than 6 months) declared as part of the LTS+ release. At the end of the “migration window,” LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress). +- When LTS is released, it will have a declared sunset date of at most two years. The LTS will only be marked ‘Sunset’ when the date (>=2 yr) has elapsed, and a new LTS version is released. 'Sunset' in this context means the end of active support and the start of the EOL phase. +- Customers will then have a specified migration time (no less than six months) declared as part of the LTS+ release. At the end of the “migration window,” LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress). - Upon releasing I+, the current Innovation release is EOL and subject to the migration window. ## Supported Commercial Distributions diff --git a/content/versions.md b/content/versions.md index e0937a62b2..307dc2451a 100644 --- a/content/versions.md +++ b/content/versions.md @@ -13,7 +13,7 @@ product = ["automate", "client", "server", "habitat", "inspec", "supermarket", " weight = 30 +++ -This section lists the free and commercial Chef products and versions we currently support and will continue to support until the end of year 2024 or till Infra Client 18 is End of Life (which ever happens first). The lifecycle stage defines the involvement by Chef Software in updating and maintaining each product. +This section lists the free and commercial Chef products and versions we currently support and will continue to support until the end of 2024 or until Infra Client 18 is End of Life (whichever happens first). The lifecycle stage defines Chef Software's involvement in updating and maintaining each product. ## Lifecycle Definitions From 1f3b4b4bb3eebca0c58d44714906a15f4b9460dd Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Wed, 28 Aug 2024 15:36:47 +0530 Subject: [PATCH 03/11] changes updated Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/supported_versions.md b/content/supported_versions.md index 3889f1e0eb..ed118f993a 100644 --- a/content/supported_versions.md +++ b/content/supported_versions.md @@ -72,7 +72,7 @@ The following describes the general impact of a product reaching EOL. For more d - This stage indicates that Progress has set a date after which the application or version will no longer be supported or recommended for customers' use. - Products covered by active maintenance and support services at the time of an announced EOL will continue receiving Technical Support on the same terms as Sunset product releases for the duration of the purchased maintenance and support services. - Progress does not allow renewal of maintenance and support services for EOL products. -- Once the existing maintenance and support services expire, Progress will not provide any further enhancements or fixes or entertain any new support cases. The existing product documentation, knowledgebase articles, and online user community discussions will remain the only support. +- Once the existing maintenance and support services expire, Progress will not provide any further enhancements or fixes or entertain any new support cases. The existing product documentation, knowledge base articles, and online user community discussions will remain the only support. For more details on the Chef on Prem Life Cycle Policy, click here ### Versions and Status From 031107c7d9ca2a3014fb4d7e56b0e9708a551847 Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Wed, 28 Aug 2024 15:42:14 +0530 Subject: [PATCH 04/11] fixed markdown lint errors Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 11 ++++++----- content/versions.md | 2 +- 2 files changed, 7 insertions(+), 6 deletions(-) diff --git a/content/supported_versions.md b/content/supported_versions.md index ed118f993a..de8629f98d 100644 --- a/content/supported_versions.md +++ b/content/supported_versions.md @@ -73,7 +73,8 @@ The following describes the general impact of a product reaching EOL. For more d - Products covered by active maintenance and support services at the time of an announced EOL will continue receiving Technical Support on the same terms as Sunset product releases for the duration of the purchased maintenance and support services. - Progress does not allow renewal of maintenance and support services for EOL products. - Once the existing maintenance and support services expire, Progress will not provide any further enhancements or fixes or entertain any new support cases. The existing product documentation, knowledge base articles, and online user community discussions will remain the only support. -For more details on the Chef on Prem Life Cycle Policy, click here + +To know more about the Chef's Prem Life Cycle Policy, see [Prem Life Cycle Policy]. ### Versions and Status @@ -81,7 +82,7 @@ Progress Chef has transitioned from N-1 and N-2 Support Policy to LTS++ and I++ - LTS for Progress Chef will be for three years. - LTS will follow the released version. - - For Example, Chef Infra 19 LTS is a significant version. All minor releases are like 19. X and patches are like 19.2.x and will fall under LTS support. + - For Example, Chef Infra 19 LTS is a significant version. All minor releases are like 19. X and patches are like 19.2.x and will fall under LTS support. - As the Product EOL date is predetermined, a new release is not required to publish this message. - There can be more than one Innovation release between the next LTS release. For example, Chef Infra 20 and 22 will be an Innovation Release, and the next LTS release can be Chef 23 LTS. - When LTS is released, it will have a declared sunset date of at most two years. The LTS will only be marked ‘Sunset’ when the date (>=2 yr) has elapsed, and a new LTS version is released. 'Sunset' in this context means the end of active support and the start of the EOL phase. @@ -96,8 +97,8 @@ Use of these and later versions of these distributions must be by the Chef End U |-------------------|---------|---------|------------------|--------------|---------------------------------------| | Chef Courier | 1.0 | I | GA | | 6 months after the release of I+ | | Chef 360 Platform | 1.0 | I | GA | | 6 months after the release of I+ | -| Chef Infra Client | 19 | LTS | GA | | 3 years or more from the release date | -| Chef InSpec | 7 | LTS | GA | | 3 years or more from the release date | +| Chef Infra Client | 19 | LTS | GA | TBD | 3 years or more from the release date | +| Chef InSpec | 7 | LTS | GA | TBD | 3 years or more from the release date | {{< note >}} Chef Backend does not directly require acceptance of the Chef EULA, but it does have functionality that requires its acceptance in other products. {{< /note >}} @@ -135,7 +136,7 @@ The following products are deprecated, so move to newer versions or products. | Chef Push Jobs | All | EOL | December 31, 2020 | | Chef Replication/Sync | All | EOL | August 31, 2019 | | Chef Server DRBD HA | All | EOL | March 31, 2019 | -| Chef Workflow (Delivery) | All | EOL | December 31, 2020 | +| Chef Workflow (Delivery) | All | EOL | December 31, 2020 | | Chef Workstation | 20.12.205 and under | EOL | December 31, 2021 | | Enterprise Chef | All | EOL | December 31, 2018 | | Reporting | All | EOL | December 31, 2018 | diff --git a/content/versions.md b/content/versions.md index 307dc2451a..705deb4d30 100644 --- a/content/versions.md +++ b/content/versions.md @@ -44,7 +44,7 @@ Chef Infra Client generally follows an N-1 support strategy. This means that if Unless otherwise stated, versions older than those listed below are EOL. -Chef Infra Client 19 and other chef products that will launch after Infra client 19 will follow new long term support policy. Please refer our new page for for more details. +Chef Infra Client 19 and other chef products that will launch after Infra client 19 will follow new long term support policy. Please refer our new page for [supported version] for more details. {{< /important >}} From 3cf2bb84dcfca1c41ad5c7e23a8062d36d791339 Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Wed, 28 Aug 2024 15:47:00 +0530 Subject: [PATCH 05/11] fixed buildkite errors Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/supported_versions.md b/content/supported_versions.md index de8629f98d..826cddc0b3 100644 --- a/content/supported_versions.md +++ b/content/supported_versions.md @@ -30,7 +30,7 @@ Progress Chef runs different releases that can run in parallel, and our customer - The software will get support depending on the timeline decided with LTS. - Upgrade planning is more manageable for customers since they know when the next LTS version will be out. -### Non-Supported (NS) Releases – Technical/Private Preview/Alpha/Beta Release +### Non-Supported (NS) Releases - Technical/Private Preview/Alpha/Beta Release - Progress may offer Technical/Private Previews containing Technical Preview Features on a Progress-hosted environment under the terms in the applicable End User License Agreement. - Progress may preview Features/Products planned to be released as future LTS features/products so that customers can validate if new features/products meet their use case and provide early feedback to Progress ahead of a general release. @@ -85,8 +85,8 @@ Progress Chef has transitioned from N-1 and N-2 Support Policy to LTS++ and I++ - For Example, Chef Infra 19 LTS is a significant version. All minor releases are like 19. X and patches are like 19.2.x and will fall under LTS support. - As the Product EOL date is predetermined, a new release is not required to publish this message. - There can be more than one Innovation release between the next LTS release. For example, Chef Infra 20 and 22 will be an Innovation Release, and the next LTS release can be Chef 23 LTS. -- When LTS is released, it will have a declared sunset date of at most two years. The LTS will only be marked ‘Sunset’ when the date (>=2 yr) has elapsed, and a new LTS version is released. 'Sunset' in this context means the end of active support and the start of the EOL phase. -- Customers will then have a specified migration time (no less than six months) declared as part of the LTS+ release. At the end of the “migration window,” LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress). +- When LTS is released, it will have a declared sunset date of at most two years. The LTS will only be marked ‘Sunset’ when the date (>=2 yr) has elapsed, and a new LTS version is released. `Sunset` in this context means the end of active support and the start of the EOL phase. +- Customers will then have a specified migration time (no less than six months) declared as part of the LTS+ release. At the end of the "migration window", LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress). - Upon releasing I+, the current Innovation release is EOL and subject to the migration window. ## Supported Commercial Distributions From 9a13ad22c1c40c58e792dc6b392515a42c8597a3 Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Wed, 28 Aug 2024 15:48:19 +0530 Subject: [PATCH 06/11] fixed buildkite errors Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/supported_versions.md b/content/supported_versions.md index 826cddc0b3..ee4cb7235e 100644 --- a/content/supported_versions.md +++ b/content/supported_versions.md @@ -85,7 +85,7 @@ Progress Chef has transitioned from N-1 and N-2 Support Policy to LTS++ and I++ - For Example, Chef Infra 19 LTS is a significant version. All minor releases are like 19. X and patches are like 19.2.x and will fall under LTS support. - As the Product EOL date is predetermined, a new release is not required to publish this message. - There can be more than one Innovation release between the next LTS release. For example, Chef Infra 20 and 22 will be an Innovation Release, and the next LTS release can be Chef 23 LTS. -- When LTS is released, it will have a declared sunset date of at most two years. The LTS will only be marked ‘Sunset’ when the date (>=2 yr) has elapsed, and a new LTS version is released. `Sunset` in this context means the end of active support and the start of the EOL phase. +- When LTS is released, it will have a declared sunset date of at most two years. The LTS will only be marked `Sunset` when the date (>=2 yr) has elapsed, and a new LTS version is released. `Sunset` in this context means the end of active support and the start of the EOL phase. - Customers will then have a specified migration time (no less than six months) declared as part of the LTS+ release. At the end of the "migration window", LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress). - Upon releasing I+, the current Innovation release is EOL and subject to the migration window. From a949710049c1a1742f55a4318514e6a265d7bf3c Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Wed, 28 Aug 2024 16:33:59 +0530 Subject: [PATCH 07/11] minor doc fixes Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 76 ++++++++++++++++++----------------- 1 file changed, 40 insertions(+), 36 deletions(-) diff --git a/content/supported_versions.md b/content/supported_versions.md index ee4cb7235e..624c25da6c 100644 --- a/content/supported_versions.md +++ b/content/supported_versions.md @@ -13,35 +13,37 @@ product = ["automate", "client", "server", "habitat", "inspec", "supermarket", " weight = 35 +++ -This section lists the free and commercial On-Premises Chef products and versions we support based on our new Long-term support policy. This policy, which defines Chef Software's involvement in updating and maintaining each product, has significant implications for our customers and their products. +This section lists the free and commercial On-Premises Chef products and versions we support based on our new long-term support policy. This policy, which defines Chef Software's involvement in updating and maintaining each product, has significant implications for our customers and their products. -## Product Releases +## Product releases -Progress Chef runs different releases that can run in parallel, and our customers can adapt them based on their needs. Following are releases chef supports: +Chef runs different releases that can run in parallel, and our customers can adapt them based on their needs. Following are releases of Chef supports: -### Innovation (I) Release +### Innovation (I) release - Innovation releases are designed for customers seeking faster modernization and innovation. Progress recommends using continuous integration and continuous delivery to help benefit from the more rapid release cadence. Innovation releases also allow all customers to explore features appearing in future LTS releases. -- With the introduction of LTS in Chef, any other major release will be termed an Innovation Release. This release will be flexible and allow Progress Chef to release significant versions and new features without LTS. +- With the introduction of LTS in Chef, any other major release will be termed an Innovation release. This release will be flexible and allow Chef to release significant versions and new features without LTS. -### Long-Term Supported (LTS) Release +### Long-term supported (LTS) release -- From time to time, Progress may elect to designate a new release as Long-Term Supported (LTS). Customers who primarily look for stability and minimal change for their implementation over many years can adapt to the LTS release. +- From time to time, Chef may elect to designate a new release as long-term supported (LTS). Customers who primarily look for stability and minimal change for their implementation over many years can adapt to the LTS release. - The software will get support depending on the timeline decided with LTS. - Upgrade planning is more manageable for customers since they know when the next LTS version will be out. -### Non-Supported (NS) Releases - Technical/Private Preview/Alpha/Beta Release +### Non-supported (NS) releases -- Progress may offer Technical/Private Previews containing Technical Preview Features on a Progress-hosted environment under the terms in the applicable End User License Agreement. -- Progress may preview Features/Products planned to be released as future LTS features/products so that customers can validate if new features/products meet their use case and provide early feedback to Progress ahead of a general release. +Non-supported releases are ad hoc releases made according to the requirement. They can be technical, private preview, alpha, or beta release. + +- Progress may offer technical/private previews containing technical preview features on a Progress hosted environment under the terms in the applicable End User License Agreement. +- Progress may preview features/products planned to be released as future LTS features/products so that customers can validate if new features/products meet their use case and provide early feedback to Progress ahead of a general release. - This release does not include CVE fixes, which Progress may choose to do. -- Customers must move to GA release once GA is available for Chef products. We do not provide any support for any release candidates such as Alpha Beta or Private Preview post the GA launch. +- Customers must move to GA release once GA is available for Chef products. We do not provide any support for any release candidates such as alpha, beta, or a private preview post the GA launch. -### Lifecycle Definitions +## Lifecycle definitions - Each Innovation and LTS release has its lifecycle starting at GA, migrates, and ends as described below: -### Generally Available (GA) +### Generally available (GA) This stage indicates that the product or version is actively developing and maintaining. @@ -50,50 +52,50 @@ This stage indicates that the product or version is actively developing and main - Chef welcomes customer feature requests for the product roadmap for the application. - Progress will evaluate GA releases for certifications of new third-party products, including new operating system versions. If you are porting to a new operating system that has not previously been supported, the LTS versions will be considered. -### Migration Phase (MP) +### Migration phase (MP) -- An LTS/I release enters the Migration Phase with the launch of the LTS+/I+ release. When the Sunset Phase starts, in parallel, the Migration Phase starts, which is the transition period provided to customers to move to LTS+/I+. -- LTS and Innovation releases in the Migration Phase are fully supported. Progress will evaluate them for certifications on new operating environments but not for ports to new hardware systems. -- If you encounter any problems using product releases in the Migration Phase, Progress will work with customers toward an appropriate resolution where possible if active maintenance and support services cover their licenses. +- An LTS/I release enters the Migration phase with the launch of the LTS+/I+ release. When the Sunset phase starts, in parallel, the Migration phase starts, which is the transition period provided to customers to move to LTS+/I+. +- LTS and Innovation releases in the Migration phase are fully supported. Progress will evaluate them for certifications on new operating environments but not for ports to new hardware systems. +- If you encounter any problems using product releases in the Migration phase, Progress will work with customers toward an appropriate resolution where possible if active maintenance and support services cover their licenses. -### Sunset Phase (Only for LTS releases) +### Sunset phase (only for LTS releases) -- After fulfilling the following conditions, an LTS release enters the Sunset Phase. +- After fulfilling the following conditions, an LTS release enters the Sunset phase. - When the launch of the release is for two or more years, and - A new LTS version has been released. - The Sunset phase does not apply to Innovation releases. Once a subsequent Innovation release becomes available, the prior Innovation release immediately moves to the EOL life cycle phase with a given period of migration phase. -- If you face any problem using product releases in the Sunset Phase, Progress will work with customers towards an appropriate resolution where possible if active maintenance and support services cover their licenses. The resolution includes the possibility of an Update provided by Progress. We are committed to continuous support even during the Sunset Phase, ensuring your confidence in our products. -- Progress only provides standard support for the LTS release in the Sunset Phase if the customer has opted for Extended Paid Support. Progress recommends that customers plan to upgrade from Sunset Phase product releases using this document as a guideline. +- If you face any problem using product releases in the Sunset phase, Progress will work with customers towards an appropriate resolution where possible if active maintenance and support services cover their licenses. The resolution includes the possibility of an update provided by Progress. We are committed to continuous support even during the Sunset phase, ensuring your confidence in our products. +- Progress only provides standard support for the LTS release in the Sunset phase if the customer has opted for Extended Paid Support. Progress recommends that customers plan to upgrade from Sunset phase product releases using this document as a guideline. -### End Of Life (EOL) Phase +### End of Life (EOL) phase The following describes the general impact of a product reaching EOL. For more details, refer to the official EOL communication, usually emailing. You can also find this information [here]. - This stage indicates that Progress has set a date after which the application or version will no longer be supported or recommended for customers' use. -- Products covered by active maintenance and support services at the time of an announced EOL will continue receiving Technical Support on the same terms as Sunset product releases for the duration of the purchased maintenance and support services. +- Products covered by active maintenance and support services at the time of an announced EOL will continue receiving technical support on the same terms as Sunset product releases for the duration of the purchased maintenance and support services. - Progress does not allow renewal of maintenance and support services for EOL products. - Once the existing maintenance and support services expire, Progress will not provide any further enhancements or fixes or entertain any new support cases. The existing product documentation, knowledge base articles, and online user community discussions will remain the only support. -To know more about the Chef's Prem Life Cycle Policy, see [Prem Life Cycle Policy]. +To know more about the Chef's prem life cycle policy, see [Prem Life Cycle Policy]. -### Versions and Status +### Versions and status -Progress Chef has transitioned from N-1 and N-2 Support Policy to LTS++ and I++ Support Strategy. The Support strategy works like follows: +Chef has transitioned from N-1 and N-2 support policy to LTS++ and I++ support strategy. The support strategy works like follows: -- LTS for Progress Chef will be for three years. +- LTS for Chef will be for three years. - LTS will follow the released version. - - For Example, Chef Infra 19 LTS is a significant version. All minor releases are like 19. X and patches are like 19.2.x and will fall under LTS support. -- As the Product EOL date is predetermined, a new release is not required to publish this message. -- There can be more than one Innovation release between the next LTS release. For example, Chef Infra 20 and 22 will be an Innovation Release, and the next LTS release can be Chef 23 LTS. + - For Example, Chef Infra Server 19 LTS is a significant version. All minor releases are like 19. X and patches are like 19.2.x and will fall under LTS support. +- As the product EOL date is predetermined, a new release is not required to publish this message. +- There can be more than one Innovation release between the next LTS release. For example, Chef Infra Server 20 and 22 will be an Innovation release, and the next LTS release can be Chef 23 LTS. - When LTS is released, it will have a declared sunset date of at most two years. The LTS will only be marked `Sunset` when the date (>=2 yr) has elapsed, and a new LTS version is released. `Sunset` in this context means the end of active support and the start of the EOL phase. - Customers will then have a specified migration time (no less than six months) declared as part of the LTS+ release. At the end of the "migration window", LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress). - Upon releasing I+, the current Innovation release is EOL and subject to the migration window. -## Supported Commercial Distributions +## Supported commercial distributions Use of these and later versions of these distributions must be by the Chef End User License Agreement or a commercial agreement with the Chef. Additional information is available in this announcement. -| Product | Version | Release | Lifecycle Status | Release Date | EOL Date | +| Product | Version | Release | Lifecycle status | Release date | EOL date | |-------------------|---------|---------|------------------|--------------|---------------------------------------| | Chef Courier | 1.0 | I | GA | | 6 months after the release of I+ | | Chef 360 Platform | 1.0 | I | GA | | 6 months after the release of I+ | @@ -102,11 +104,11 @@ Use of these and later versions of these distributions must be by the Chef End U {{< note >}} Chef Backend does not directly require acceptance of the Chef EULA, but it does have functionality that requires its acceptance in other products. {{< /note >}} -## Supported Free Distributions < to be updated by Eng.> +## Supported free distributions < to be updated by Eng.> Use of the following distributions is governed by the Apache License, version 2.0. -| Product | Version | Lifecycle Status | EOL Date | +| Product | Version | Lifecycle status | EOL date | |-------------|---------|------------------|----------| | Supermarket | 5.x | GA | TBD | @@ -114,12 +116,14 @@ Use of the following distributions is governed by the Apache License, version 2. The following products are deprecated, so move to newer versions or products. -| Product | Version | Lifecycle Status | EOL Date | +| Product | Version | Lifecycle status | EOL date | |-------------------|---------|------------------|----------| | Chef Infra Client | 18.x | TBD | TBD | | Chef InSpec | 6.x | TBD | TBD | -## End of Life (EOL) Products < this list should remain the same and must be maintained in the future according to new policy> +## End of Life (EOL) products + +The following list must be maintained in the future according to new policy. | Product | Version | Lifecycle Status | EOL Date | |--------------------------|---------------------|------------------|-------------------| From 70fdfcf98292fa0c8dbd1dc8d39b7874c0ccf571 Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Wed, 28 Aug 2024 16:37:45 +0530 Subject: [PATCH 08/11] added links Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/supported_versions.md b/content/supported_versions.md index 624c25da6c..49a769e9a3 100644 --- a/content/supported_versions.md +++ b/content/supported_versions.md @@ -93,7 +93,7 @@ Chef has transitioned from N-1 and N-2 support policy to LTS++ and I++ support s ## Supported commercial distributions -Use of these and later versions of these distributions must be by the Chef End User License Agreement or a commercial agreement with the Chef. Additional information is available in this announcement. +Use of these and later versions of these distributions must be by the [Chef End User License Agreement](https://www.chef.io/end-user-license-agreement) or a commercial agreement with the Chef. Additional information is available in our blog post of [Introducing the New Chef](https://www.chef.io/blog/chef-software-announces-the-enterprise-automation-stack). | Product | Version | Release | Lifecycle status | Release date | EOL date | |-------------------|---------|---------|------------------|--------------|---------------------------------------| From bb80df86a3a7c864243704eb5b3d6fed91c0bb85 Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Thu, 29 Aug 2024 23:09:30 +0530 Subject: [PATCH 09/11] made changes to the version docs Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 14 +++++++------- content/versions.md | 8 +++++--- 2 files changed, 12 insertions(+), 10 deletions(-) diff --git a/content/supported_versions.md b/content/supported_versions.md index 49a769e9a3..405512a6d0 100644 --- a/content/supported_versions.md +++ b/content/supported_versions.md @@ -1,5 +1,5 @@ +++ -title = "Supported Versions(LTS/Innovation)" +title = "Future Supported Versions (LTS/Innovation)" draft = false gh_repo = "chef-web-docs" aliases = ["/versions.html"] @@ -7,8 +7,8 @@ product = ["automate", "client", "server", "habitat", "inspec", "supermarket", " [menu] [menu.overview] - title = "Supported Versions(LTS/Innovation)" - identifier = "overview/packages_&_platforms/supported_versions.md Supported Versions(LTS/Innovation)" + title = "Future Supported Versions" + identifier = "overview/packages_&_platforms/supported_versions.md Future Supported Versions(LTS/Innovation)" parent = "overview/packages_&_platforms" weight = 35 +++ @@ -17,12 +17,12 @@ This section lists the free and commercial On-Premises Chef products and version ## Product releases -Chef runs different releases that can run in parallel, and our customers can adapt them based on their needs. Following are releases of Chef supports: +Progress Chef runs different releases that can run in parallel, and our customers can adapt them based on their needs. Following are releases of Chef supports: ### Innovation (I) release - Innovation releases are designed for customers seeking faster modernization and innovation. Progress recommends using continuous integration and continuous delivery to help benefit from the more rapid release cadence. Innovation releases also allow all customers to explore features appearing in future LTS releases. -- With the introduction of LTS in Chef, any other major release will be termed an Innovation release. This release will be flexible and allow Chef to release significant versions and new features without LTS. +- With the introduction of LTS in Chef, any other major release will be termed an Innovation release. This release will be flexible and allow Progress Chef to release significant versions and new features without LTS. ### Long-term supported (LTS) release @@ -80,9 +80,9 @@ To know more about the Chef's prem life cycle policy, see [Prem Life Cycle Polic ### Versions and status -Chef has transitioned from N-1 and N-2 support policy to LTS++ and I++ support strategy. The support strategy works like follows: +Progress Chef has transitioned from N-1 and N-2 support policy to LTS++ and I++ support strategy. The support strategy works like follows: -- LTS for Chef will be for three years. +- LTS for Progress Chef will be for three years. - LTS will follow the released version. - For Example, Chef Infra Server 19 LTS is a significant version. All minor releases are like 19. X and patches are like 19.2.x and will fall under LTS support. - As the product EOL date is predetermined, a new release is not required to publish this message. diff --git a/content/versions.md b/content/versions.md index 705deb4d30..6a885a269e 100644 --- a/content/versions.md +++ b/content/versions.md @@ -1,5 +1,5 @@ +++ -title = "Supported Versions(till 2024)" +title = "Current Supported Versions" draft = false gh_repo = "chef-web-docs" aliases = ["/versions.html"] @@ -7,12 +7,14 @@ product = ["automate", "client", "server", "habitat", "inspec", "supermarket", " [menu] [menu.overview] - title = "Supported Versions(till 2024)" - identifier = "overview/packages_&_platforms/versions.md Supported Versions(till 2024)" + title = "Current Supported Versions" + identifier = "overview/packages_&_platforms/versions.md Current Supported Versions" parent = "overview/packages_&_platforms" weight = 30 +++ +{{< note >}} These supported versions will last until the LTS/Innovation comes into force at the end of the year 2024. {{< /note >}} + This section lists the free and commercial Chef products and versions we currently support and will continue to support until the end of 2024 or until Infra Client 18 is End of Life (whichever happens first). The lifecycle stage defines Chef Software's involvement in updating and maintaining each product. ## Lifecycle Definitions From 1da7bab62b20e4060ed038c6661566a2f2325385 Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Thu, 29 Aug 2024 23:11:07 +0530 Subject: [PATCH 10/11] made changes to the version docs Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/supported_versions.md b/content/supported_versions.md index 405512a6d0..078b330d3d 100644 --- a/content/supported_versions.md +++ b/content/supported_versions.md @@ -2,7 +2,6 @@ title = "Future Supported Versions (LTS/Innovation)" draft = false gh_repo = "chef-web-docs" -aliases = ["/versions.html"] product = ["automate", "client", "server", "habitat", "inspec", "supermarket", "workstation"] [menu] From f4f2a7a9ab5cb0b0f2134e4746d8fca1d3f7222d Mon Sep 17 00:00:00 2001 From: Dishank Tiwari Date: Sat, 31 Aug 2024 15:13:37 +0530 Subject: [PATCH 11/11] updated the doc Signed-off-by: Dishank Tiwari --- content/supported_versions.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/content/supported_versions.md b/content/supported_versions.md index 078b330d3d..6add0c1f6c 100644 --- a/content/supported_versions.md +++ b/content/supported_versions.md @@ -20,7 +20,7 @@ Progress Chef runs different releases that can run in parallel, and our customer ### Innovation (I) release -- Innovation releases are designed for customers seeking faster modernization and innovation. Progress recommends using continuous integration and continuous delivery to help benefit from the more rapid release cadence. Innovation releases also allow all customers to explore features appearing in future LTS releases. +- Innovation releases are designed for customers seeking faster modernization and innovation. Progress Chef recommends using continuous integration and continuous delivery to help benefit from the more rapid release cadence. Innovation releases also allow all customers to explore features appearing in future LTS releases. - With the introduction of LTS in Chef, any other major release will be termed an Innovation release. This release will be flexible and allow Progress Chef to release significant versions and new features without LTS. ### Long-term supported (LTS) release @@ -33,9 +33,9 @@ Progress Chef runs different releases that can run in parallel, and our customer Non-supported releases are ad hoc releases made according to the requirement. They can be technical, private preview, alpha, or beta release. -- Progress may offer technical/private previews containing technical preview features on a Progress hosted environment under the terms in the applicable End User License Agreement. -- Progress may preview features/products planned to be released as future LTS features/products so that customers can validate if new features/products meet their use case and provide early feedback to Progress ahead of a general release. -- This release does not include CVE fixes, which Progress may choose to do. +- Progress Chef may offer technical/private previews containing technical preview features on a Progress Chef hosted environment under the terms in the applicable End User License Agreement. +- Progress Chef may preview features/products planned to be released as future LTS features/products so that customers can validate if new features/products meet their use case and provide early feedback to Progress Chef ahead of a general release. +- This release does not include CVE fixes, which Progress Chef may choose to do. - Customers must move to GA release once GA is available for Chef products. We do not provide any support for any release candidates such as alpha, beta, or a private preview post the GA launch. ## Lifecycle definitions @@ -46,16 +46,16 @@ Non-supported releases are ad hoc releases made according to the requirement. Th This stage indicates that the product or version is actively developing and maintaining. -- GA releases are fully supported (LTS or Innovation). If you face any problems, Progress will work with you to find an appropriate resolution if active maintenance and support services cover them. +- GA releases are fully supported (LTS or Innovation). If you face any problems, Progress Chef will work with you to find an appropriate resolution if active maintenance and support services cover them. - Chef continues to provide releases to the application or version in response to customer needs and security vulnerabilities. - Chef welcomes customer feature requests for the product roadmap for the application. -- Progress will evaluate GA releases for certifications of new third-party products, including new operating system versions. If you are porting to a new operating system that has not previously been supported, the LTS versions will be considered. +- Progress Chef will evaluate GA releases for certifications of new third-party products, including new operating system versions. If you are porting to a new operating system that has not previously been supported, the LTS versions will be considered. ### Migration phase (MP) - An LTS/I release enters the Migration phase with the launch of the LTS+/I+ release. When the Sunset phase starts, in parallel, the Migration phase starts, which is the transition period provided to customers to move to LTS+/I+. -- LTS and Innovation releases in the Migration phase are fully supported. Progress will evaluate them for certifications on new operating environments but not for ports to new hardware systems. -- If you encounter any problems using product releases in the Migration phase, Progress will work with customers toward an appropriate resolution where possible if active maintenance and support services cover their licenses. +- LTS and Innovation releases in the Migration phase are fully supported. Progress Chef will evaluate them for certifications on new operating environments but not for ports to new hardware systems. +- If you encounter any problems using product releases in the Migration phase, Progress Chef will work with customers toward an appropriate resolution where possible if active maintenance and support services cover their licenses. ### Sunset phase (only for LTS releases) @@ -63,17 +63,17 @@ This stage indicates that the product or version is actively developing and main - When the launch of the release is for two or more years, and - A new LTS version has been released. - The Sunset phase does not apply to Innovation releases. Once a subsequent Innovation release becomes available, the prior Innovation release immediately moves to the EOL life cycle phase with a given period of migration phase. -- If you face any problem using product releases in the Sunset phase, Progress will work with customers towards an appropriate resolution where possible if active maintenance and support services cover their licenses. The resolution includes the possibility of an update provided by Progress. We are committed to continuous support even during the Sunset phase, ensuring your confidence in our products. -- Progress only provides standard support for the LTS release in the Sunset phase if the customer has opted for Extended Paid Support. Progress recommends that customers plan to upgrade from Sunset phase product releases using this document as a guideline. +- If you face any problem using product releases in the Sunset phase, Progress Chef will work with customers towards an appropriate resolution where possible if active maintenance and support services cover their licenses. The resolution includes the possibility of an update provided by Progress Chef. We are committed to continuous support even during the Sunset phase, ensuring your confidence in our products. +- Progress Chef only provides standard support for the LTS release in the Sunset phase if the customer has opted for Extended Paid Support. Progress Chef recommends that customers plan to upgrade from Sunset phase product releases using this document as a guideline. ### End of Life (EOL) phase The following describes the general impact of a product reaching EOL. For more details, refer to the official EOL communication, usually emailing. You can also find this information [here]. -- This stage indicates that Progress has set a date after which the application or version will no longer be supported or recommended for customers' use. +- This stage indicates that Progress Chef has set a date after which the application or version will no longer be supported or recommended for customers' use. - Products covered by active maintenance and support services at the time of an announced EOL will continue receiving technical support on the same terms as Sunset product releases for the duration of the purchased maintenance and support services. -- Progress does not allow renewal of maintenance and support services for EOL products. -- Once the existing maintenance and support services expire, Progress will not provide any further enhancements or fixes or entertain any new support cases. The existing product documentation, knowledge base articles, and online user community discussions will remain the only support. +- Progress Chef does not allow renewal of maintenance and support services for EOL products. +- Once the existing maintenance and support services expire, Progress Chef will not provide any further enhancements or fixes or entertain any new support cases. The existing product documentation, knowledge base articles, and online user community discussions will remain the only support. To know more about the Chef's prem life cycle policy, see [Prem Life Cycle Policy]. @@ -87,7 +87,7 @@ Progress Chef has transitioned from N-1 and N-2 support policy to LTS++ and I++ - As the product EOL date is predetermined, a new release is not required to publish this message. - There can be more than one Innovation release between the next LTS release. For example, Chef Infra Server 20 and 22 will be an Innovation release, and the next LTS release can be Chef 23 LTS. - When LTS is released, it will have a declared sunset date of at most two years. The LTS will only be marked `Sunset` when the date (>=2 yr) has elapsed, and a new LTS version is released. `Sunset` in this context means the end of active support and the start of the EOL phase. -- Customers will then have a specified migration time (no less than six months) declared as part of the LTS+ release. At the end of the "migration window", LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress). +- Customers will then have a specified migration time (no less than six months) declared as part of the LTS+ release. At the end of the "migration window", LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress Chef). - Upon releasing I+, the current Innovation release is EOL and subject to the migration window. ## Supported commercial distributions