Skip to content

chore: removing obsolete / deprecated EoL .Net 3.1, 5.0, 6.0 #627

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ibuziuk
Copy link
Collaborator

@ibuziuk ibuziuk commented Aug 11, 2025

Description of Changes

Deprecation Status of .NET Versions
NET 3.1 was a Long-Term Support (LTS) release, but its support ended on December 13, 2022. Since then, it has been considered deprecated.

NET 5.0 was a Standard Term Support (STS) release, and its support ended much earlier, on May 10, 2022, making it a deprecated version. STS releases have a shorter lifecycle of 18 months.

NET 6.0 was also a Long-Term Support (LTS) release, but its support officially ended on November 12, 2024. This makes it a deprecated version.

Related Issue(s)

Link the GitHub/GitLab/JIRA issues that are related to this PR.

Acceptance Criteria

  • Contributing guide

Have you read the devfile registry contributing guide and followed its instructions?

  • Test automation

Does this repository's tests pass with your changes?

  • Documentation

Does any documentation need to be updated with your changes?

  • Check Tools Provider

Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

Tests Performed

Explain what tests you personally ran to ensure the changes are functioning as expected.

How To Test

Instructions for the reviewer on how to test your changes.

Notes To Reviewer

Any notes you would like to include for the reviewer.

@ibuziuk ibuziuk requested review from kadel and a team as code owners August 11, 2025 13:21
@openshift-ci openshift-ci bot requested review from johnmcollier and thepetk August 11, 2025 13:21
Copy link

openshift-ci bot commented Aug 11, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ibuziuk
Once this PR has been reviewed and has the lgtm label, please assign thepetk for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

@thepetk thepetk left a comment

Choose a reason for hiding this comment

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

According to the lifecycle policy we have in place, we could start by adding the deprecated tag in the stack and then after a 3 months period remove it.

In case we decide to keep open this PR, we need also to remove the records from the CODEOWNERS file:

# .Net stacks

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented Aug 11, 2025

@thepetk sorry, but why can't we just remove it? Runtime deprecation happened a long time ago on the Microsoft's end, and on the devfile.io landing page [1] you currently promote obsolete samples at the first place that probably no one is using -

[1] https://registry.devfile.io/viewer

Signed-off-by: Ilya Buziuk <[email protected]>
@ibuziuk ibuziuk requested a review from a team as a code owner August 11, 2025 14:56
Copy link

openshift-ci bot commented Aug 11, 2025

@ibuziuk: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/v4.16-registry-test 6624046 link true /test v4.16-registry-test
ci/prow/v4.16-images 6624046 link true /test v4.16-images

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

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.

2 participants