List full release history

kubernetes / website

Kubernetes website and documentation repo:

https://kubernetes.io

Creative Commons Attribution 4.0 International

4.46k stars 14.37k forks source link

List full release history #43837

Open sftim opened 11 months ago

sftim commented 11 months ago

This is a Feature Request

What would you like to be added Show all the release history (minor release level) on https://kubernetes.io/releases/

Why is this needed People want to find out when older releases happened, to find out whether those are still in support and how long they've been out of support. I had that need just now.

Comments

Personally I'd have the out-of-support releases hidden by default, with a checkbox you activate to show the older releases. Maybe a special color for the out-of-support minor releases too.

We have partial data (doesn't cover 1.0 or 1.1) in https://github.com/kubernetes/website/blob/8f7251566c831cfea5adce977d7a4fac39714bab/data/releases/eol.yaml

/sig release /kind feature /language en

coder12git commented 10 months ago

@sftim I want to work on this issue . Can you please add triage/accepted label to this?

coder12git commented 10 months ago

My approach will be this -

I will add a line after this line with a checkbox , which when user will click then they can see the release history of minor versions.
Also, I'll add a red color (probably) as a background-color to those minor versions to indicate that they are out-of-support.

coder12git commented 10 months ago

/assign

sftim commented 10 months ago

@sftim … can you please add triage/accepted label to this?

I sometimes triage the issues that I've filed myself, but - even as a tech lead - other times I hope that a different contributor will come along and make their own decision about whether to accepted it.

This is an issue where I recommend not working too much on it until someone has triaged it as accepted.

k8s-triage-robot commented 7 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 6 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

T-Lakshmi commented 6 months ago

/remove-lifecycle rotten I believe it is beneficial to have this improvement.

seokho-son commented 4 months ago

+1 Let me /triage accepted

steve-hardman commented 4 months ago

I see theer is table here:- https://kubernetes.io/releases/patch-releases/#non-active-branch-history with details of past release history.

@sftim Is this issue asking to use the data from that table to put in different format in different page at https://kubernetes.io/releases/ or I have misunderstood the request. Sorry if it not a valid question.

sftim commented 4 months ago

We have partial data (doesn't cover 1.0 or 1.1) in https://github.com/kubernetes/website/blob/8f7251566c831cfea5adce977d7a4fac39714bab/data/releases/eol.yaml

Can we fill in those gaps?