-
-
Notifications
You must be signed in to change notification settings - Fork 846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop unnecessary latest column from distros without point releases. #6608
Comments
Sounds good to me. The link will automatically switch to the Release Cycle. You just need to set I had a quick look through all the linux-distros and this seems to apply to a few more distros, where no point releases are made:
|
Thanks for the input, sounds good to me. Would you like to create a PR for all four at once? I feel only confident to change Fedora and maybe CentOS, those are the distros I'm familiar with. |
Here is a PR fixing the mismatched release dates for Fedora: |
When disabling the "releaseColumn", should the "latestReleaseDate" entries also be removed for each cycle? All they contain is redundant data. Edit: Yes, they need to be removed together with the "latest" keys, see the PRs |
Created PRs for Fedora and CentOS: |
https://endoflife.date/fedora
The differentiation between the "released" and "latest" columns doesn't really make sens here imo. Fedora gets updated all the time but there are no minor/patch versions. In all but two cases the dates are the same anyway, in those two cases I think one date is wrong.
The Fairphone page for example does not have the "latest" column and the links to each release are in the first column. I'd prefer that for Fedora, too. It would avoid duplication of data and give users a better overview.
What do you think about this? I'm happy to help with changing the yaml data but I wanted to get some feedback first. Is there something in automation which we'd need to take in consideration or which would need to be changed? (I haven't really seen or understood how the automation works around here.)
The text was updated successfully, but these errors were encountered: