search

okd-project / planning

This repository is to hold issues used in the project board
0 stars 1 forks source link

mark 3.11 version as end of life #13

Closed binnes closed 1 year ago

binnes commented 2 years ago

We need a process to 'archive' older versions of the documentation. There is a need to keep 3.11 as there are community members with 3.11 estate that is in plan to get upgraded. We also need to look at older 4.x versions too

mburke5678 commented 2 years ago

@binnes We should keep the 3.11 docs for OCP and OKD on line after EOL. We will no longer update EOL docs, however

elmiko commented 1 year ago

we discussed this issue at the okd community development meeting today. a little more context from the okd perspective is that even though OCP and Red Hat still support 3.11, the okd community is not able to support these older versions and does not plan to backport to them. we would like a way to denote in the docs that this version is not maintained by the okd community, but that the docs remain as a reference.

we are slightly concerned that the presence of the docs give the impression that the okd community supports the version, which we do not. but we acknowledge that there are community members who are still using version 3.11.

a comment from centos land, they use "end of build" to signify end of production.

binnes commented 1 year ago

Centos use End of Build - could we adopt that?

mburke5678 commented 1 year ago

@binnes Do we know what the full wording the CentOS uses? I cannot find it on the web.

binnes commented 1 year ago

@mburke5678 This is all I can find : https://www.centos.org/download/. The docs don't have anything to indicate if the version is still current/being maintained

binnes commented 1 year ago

@mburke5678 This has been implemented, but only the latest version has been left untagged. The actual version should also be left untagged, so currently 4.12 and latest should be untagged

binnes commented 1 year ago

this is implemented and reviewed in meeting 30 May