The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click here for more information.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
AAlbert1
By Level 7 Flexeran
Level 7 Flexeran

Change Title

Red Hat Package Lifecycle Date Changes and Naming convention of Releases

Class 1

Customers should be aware and be prepared

Change Summary

UPDATE: This work has now been completed (as of September 16, 2022). For full details, please see attachment Red Hat Release Info.xlsx

This notification is a continuation of the work which we announced in  March 2022.

We are going to differentiate Red Hat base package releases lifecycle dates in release tables in Technopedia. We will be implementing below changes in Technopedia: 

Base Packages: 

We are going to identify the base packages based on the discovered evidence by keeping their product names without any prefix.  We are going to classify them as base package and will update their EOL dates as follows:

Examples:   

ruby-2.0.0.648-38.el7.x86_64 

ruby-1.8.7.352-3.el6.x86_64 

 

There are two scenarios:

a.      Package versions are shared across RHEL versions (i.e., certain package versions are supported on multiple RHEL versions).


The versions and EOL for these base packages will be captured in Technopedia as follows:

Manufacturer

Product Name

Version

EOL

Notes

Red Hat

ruby

2.3 (RHEL 6)

11/30/2020

Following EOL for RHEL 6

Red Hat

ruby

2.3 (RHEL 7)

6/30/2024

Following EOL for RHEL 7

 

b.      If we cannot identify the underlying RHEL version, we will just leave the EOL empty:

Manufacturer

Product Name

Version

EOL

Notes

Red Hat

ruby

2.3

(null)

EOL undefined since RHEL version is unknown

Red Hat

ruby

2.4

(null)

EOL undefined since RHEL version is unknown

Red Hat

ruby

2.6

(null)

EOL undefined since RHEL version is unknown

 

Discovered evidence data will be mapped based on above scenarios.

Impact

This change will impact customers who rely upon Technopedia Lifecycle dates from RHEL to manage their EOL and EOS/OBS program and customers who rely on Technopedia Product ID/Release ID & Names and discovered previously mapped data to these packages.  The main changes will be to the Red Hat Base Package Lifecycle Date.  Obsolete dates for RHEL 5, 6, 7 and 8 will remain the same as currently recorded in Technopedia.

When

Customers should expect these changes on Sep 16, 2022

Reference

https://community.flexera.com/t5/Technopedia-Blog/Red-Hat-components-from-Base-Package-vs-Software-Collection-to/ba-p/225890

(1) Comment