Discrepancy in End of Life date for v1.26 in "Patch Releases" page about website HOT 6 CLOSED

We can use the notes, I forgot that we have them.

from website.

If we do an exceptional patch release, we could add an integer counter into the YAML data and a (localizable) string. The string might say words to the effect of:

“As an exception to the end-of-life policy, the Kubernetes project has made %d patch releases to Kubernetes %s to cover specific information security concerns”.

(I wouldn't actually use printf for this, and we need to use Hugo's support for numbers in localizable strings, but you get the idea).

from website.

@sftim is there a reason why we couldn't use the note option that is already there to give more context about why an additional release was created? I'm not sure how the https://github.com/kubernetes/website/blob/main/data/releases/schedule.yaml is created/maintained so maybe i'm missing some context

Either way, i think its worth making sure we list all the available releases.

/triage accepted
/priority important-longterm

from website.

/triage accepted

re-adding doing the labels

from website.

It appears that the issue has been resolved through PR #45843. We can mark this as resolved and close the issue.

/close

from website.

@dipesh-rawat: Closing this issue.

from website.