-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update CentOS support information #9382
Conversation
"name": "CentOS Stream", | ||
"link": "https://centos.org/", | ||
"architectures": [ | ||
"x64" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Builds of .NET 8 in CentOS Stream 9 are available for arm64, ppc64le, s390x and x64. For .NET 6, it is arm64, s390x and x64.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. That would be in the .NET 8 variant of this file, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The point of removing all the RHEL compatible builds (beyond RHEL) is to reduce noise with a simple statement. If there are RHEL-compatible distros with their own .NET 8 builds, then that's a different story. I'd be happy for CentOS Stream 9 (or any other distro) to be added to the .NET 8+ variants of these files if they provide their own builds. Same thing for linux.md.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be in the .NET 8 variant of this file, right?
Yes. I missed that this was .NET 8 at first. For .NET 6/CentOS Stream 9, arm64, s390x and x64 are supported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated all .NET 6, 8, and 9 files for CentOS Steam. PTAL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this supported on .NET 7? If yes, then we should update those as well to at least have the history correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.NET 7 on CentOS Stream 9 is available (at least to install) on arm64, ppc64le, s390x, and x64).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I would just add the lifecycle (and regenerate the MD files). Not sure if .NET 7 should be updated as well.
release-notes/6.0/supported-os.md
Outdated
[Red Hat Enterprise Linux][14] | 9, 8, 7 | Arm64, x64 | [Lifecycle][15] | | ||
[SUSE Enterprise Linux][16] | 15.5, 12.5 | Arm64, x64 | [Lifecycle][17] | | ||
[Ubuntu][18] | 24.04, 23.10, 22.04, 20.04 | Arm32, Arm64, x64 | [Lifecycle][19] | | ||
[CentOS][8] | | x64 | [Lifecycle][9] | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@richlander That's more a topic for distroessed
, but I think it's still good to start the discussion here as that's a nice example.
Should we add a text in the version column if there are no supported versions left? It might confuse people. We could add [None](#out-of-support-os-versions)
to make it more obvious that the information on why there's nothing can be found in the Out of Support section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That problem occurred to me and your solution is better than what I had considered. Happy to do that.
I'll update .NET 7 as well so that it matches what I did with .NET 6. Naturally, I don't want to keep updating the .NET 7 EOL information, but this change seems warranted to make it correct.
"name": "CentOS Stream", | ||
"link": "https://centos.org/", | ||
"architectures": [ | ||
"x64" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this supported on .NET 7? If yes, then we should update those as well to at least have the history correct.
Co-authored-by: Benjamin Krämer <benjamin.kraemer@jungheinrich.de> Co-authored-by: Omair Majid <omajid@redhat.com>
How does that look @Falco20019 @omajid? I think I applied all of your feedback. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Looks good to me.
Associated tool updates: richlander/distroessed#3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I also approved the PR on distroessed.
I added sections for CentOS and CentOS Stream to clarify our support position.
The intent for .NET 8+ was to rely on our RHEL compatibility statement to take care of the RHEL-compatible distros.
Doing that for .NET 6 doesn't make sense, for two reasons:
All in all, it makes good sense to clarify our position on CentOS given that CentOS 7 recently went EOL.
We'll publish a separate announcement on CentOS 7 support to provide better visibility than just this PR.
Related: https://www.redhat.com/en/blog/centos-linux-has-reached-its-end-life-eol
@Falco20019 @omajid @rbhanda