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

Fedora 35 reached end-of-life on 2022-12-13 #8084

Closed
Falco20019 opened this issue Jan 9, 2023 · 8 comments
Closed

Fedora 35 reached end-of-life on 2022-12-13 #8084

Falco20019 opened this issue Jan 9, 2023 · 8 comments

Comments

@Falco20019
Copy link
Contributor

As there seems to not be anyone in charge to create these currently, I will create some since I'm tracking them anyway.
Is it planned to be dropped for .NET Core 3.1, .NET 6.0 and .NET 7.0?

See https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html for end-of-life information.

Please add os-support label.

/CC @rbhanda @richlander
/awareness @mthalman @adegeo @MichaelSimons

@omajid
Copy link
Member

omajid commented Jan 9, 2023

Speaking as a Fedora packager, .NET packages that were part of Fedora 35 itself (eg, .NET 6.0) will stop getting updates, but will still be available, just like all other package in Fedora - like gcc, python and java-17-openjdk.

.NET 7 wasn't built in Fedora yet, so I will only be building and adding it to Fedora 36 and later.

I am not sure what the story is for external/Microsoft-built packages for .NET.

@Falco20019
Copy link
Contributor Author

Falco20019 commented Jan 10, 2023

This is mostly a reminder to update the supported OS documentation and other docs like https://learn.microsoft.com/en-us/dotnet/core/install/linux-fedora since the lifecycle policy (and also that page) state:
When a Fedora version falls out of support, .NET is no longer supported with that version.

So basically, yes, the packages remain, everything that ran should also ran in the future as there are no changes going to happen, but Microsoft will not offer any support anymore on that platform. In the past, this was reflected in the section at https://github.com/dotnet/core/blob/main/release-notes/6.0/supported-os.md#out-of-support-os-versions but was not maintained recently as other tickets of that label show.

It's also interesting to hear, that .NET 7 was not build in Fedora yet, since https://github.com/dotnet/core/blob/main/release-notes/7.0/supported-os.md#linux is stating that it supports Fedora 33+. Is this due to some backwards (or libc) compatibility or is the documentation just incorrect?

@omajid
Copy link
Member

omajid commented Jan 11, 2023

It's also interesting to hear, that .NET 7 was not build in Fedora yet, since https://github.com/dotnet/core/blob/main/release-notes/7.0/supported-os.md#linux is stating that it supports Fedora 33+. Is this due to some backwards (or libc) compatibility or is the documentation just incorrect?

It's mostly because different folks view it differently.

  • From a Fedora point of view, .NET 7 is currently under development and isn't available via the standard Fedora package repositories (in contrast to say, .NET 6, which is available in Fedora repos)
  • From a Microsoft point of view (using the downloads from dot.net) .NET 7 is supported, and available to download and use on Fedora 37

When .NET 7 is available in the Fedora repositories, the difference will disappear and the documentation will be correct either way.

@adegeo
Copy link

adegeo commented Jan 12, 2023

@omajid should we pull 35 from the doc?

@omajid
Copy link
Member

omajid commented Jan 12, 2023

@adegeo I am not sure.

How do you folks normally handle EOLs? How would you handle Windows 7 going EOL or Debian 10 going EOL?

The table at https://github.com/dotnet/core/blob/main/release-notes/7.0/supported-os.md#linux reflect's how Microsoft supports .NET 7. Can't hurt to leave Fedora 35 there.

For https://learn.microsoft.com/en-us/dotnet/core/install/linux-fedora, I think we should remove the EOL versions, but I prefer to stick with your existing policies on distro versions, whatever they are.

@adegeo
Copy link

adegeo commented Jan 16, 2023

@omajid it depends. I think when there are a lot of distro releases, having all the old versions in the docs make it too large. This wiki article, though, isn't documentation, so they can follow different rules and styles. In the actual docs we were listing unsupported versions, but recently removed them. However, if you feel there is a large user base still hitting 35 and .NET, we can keep it in the documentation and just add a note.

@omajid
Copy link
Member

omajid commented Jan 16, 2023

I made a change at dotnet/docs#33551 to address this too, let me know if that looks sensible.

@Falco20019
Copy link
Contributor Author

Fixed by #8291

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants