Skip to content

templates: Add almalinux-10 #3602

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

Merged
merged 1 commit into from
Jun 5, 2025
Merged

templates: Add almalinux-10 #3602

merged 1 commit into from
Jun 5, 2025

Conversation

refi64
Copy link
Contributor

@refi64 refi64 commented Jun 4, 2025

This adds a template for the relatively new AlmaLinux 10 release and updates the almalinux.yaml symlink.

almalinux-10.yaml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably we should bump up almalinux, rockylinux, oraclelinux, and centos-stream to 10 at once

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't mind reverting this part if needed for merge, but I don't think that's really a useful policy. All of those have somewhat different release cycles, especially CentOS Stream where 10 has been the "current" version for quite a while now, and Rocky and OL aren't even out with version 10 yet. Additionally, in practice people tend to choose one or two of them across infra, so there's no real utility to be gained from matching up all the versions.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with this. I think the unversioned template should point to the latest "stable" version. There is no reason for us to link the release schedules of different distros.

I think it would be good to write down a policy for when the unversioned templates get updated. E.g. what is the reason centos-stream.yaml still links to version 9?

Maybe we need to come up with a somewhat arbitrary definition of what "stable" means for each distro that doesn't define it itself? Even if it is something like "3 months after its initial release".

But given that Alma has Alma Kitten as upstream, I don't know why you would need to wait any longer once the project decides the current snapshot is "stable".

This adds a template for the relatively new AlmaLinux 10 release and
updates the `almalinux.yaml` symlink.

Signed-off-by: re:fi.64 <[email protected]>
@AkihiroSuda AkihiroSuda added this to the v1.1.2 milestone Jun 5, 2025
Copy link
Member

@AkihiroSuda AkihiroSuda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@AkihiroSuda AkihiroSuda merged commit 3bd8f59 into lima-vm:master Jun 5, 2025
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants