Skip to content
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

Merged
merged 11 commits into from
Jul 9, 2024
Merged

Update CentOS support information #9382

merged 11 commits into from
Jul 9, 2024

Conversation

richlander
Copy link
Member

@richlander richlander commented Jul 3, 2024

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:

  • CentOS isn't listed in the RHEL compatibility statement, only CentOS Stream.
  • .NET 6 was released in the era where there was significant confusion between CentOS and CentOS Stream.

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

"name": "CentOS Stream",
"link": "https://centos.org/",
"architectures": [
"x64"
Copy link
Member

@omajid omajid Jul 3, 2024

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.

Copy link
Member Author

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?

Copy link
Member Author

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.

Copy link
Member

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.

Copy link
Member Author

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.

Copy link
Contributor

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.

Copy link
Member

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).

Copy link
Contributor

@Falco20019 Falco20019 left a 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.

[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] |
Copy link
Contributor

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.

Copy link
Member Author

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.

release-notes/6.0/supported-os.json Show resolved Hide resolved
release-notes/8.0/supported-os.json Show resolved Hide resolved
release-notes/9.0/supported-os.json Show resolved Hide resolved
"name": "CentOS Stream",
"link": "https://centos.org/",
"architectures": [
"x64"
Copy link
Contributor

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.

richlander and others added 3 commits July 5, 2024 12:09
Co-authored-by: Benjamin Krämer <benjamin.kraemer@jungheinrich.de>
Co-authored-by: Omair Majid <omajid@redhat.com>
@richlander
Copy link
Member Author

How does that look @Falco20019 @omajid? I think I applied all of your feedback.

Copy link
Member

@omajid omajid left a 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.

@richlander
Copy link
Member Author

Associated tool updates: richlander/distroessed#3

Copy link
Contributor

@Falco20019 Falco20019 left a 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.

@richlander richlander merged commit c5016d4 into main Jul 9, 2024
2 of 4 checks passed
@richlander richlander deleted the centos-eol branch July 9, 2024 16:21
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