Skip to content

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

@ibuziuk ibuziuk requested a review from a team as a code owner August 11, 2025 14:56
@thepetk
Copy link
Contributor

thepetk commented Aug 18, 2025

@ibuziuk CI checks currently fail because #626 needs to be merged first. We are currently in the process of bumping up all devfile projects to go 1.24.

@JslYoon do you have an estimation when the #626 will be merged, so we can unblock this one?

@thepetk
Copy link
Contributor

thepetk commented Aug 18, 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

@ibuziuk as also discussed internally, according to our docs & policies in the end is up to the stack owner to decide that. As discussed @kadel (the dotnet stacks owner) is OK to remove them, so we can merge this one.

@thepetk
Copy link
Contributor

thepetk commented Aug 18, 2025

@ibuziuk per your questions for the samples -> all samples are loaded from here: https://github.com/devfile/registry/blob/main/extraDevfileEntries.yaml

Let me know if you need any further info from my side

@openshift-ci openshift-ci bot added the lgtm Looks good to me label Aug 20, 2025
Copy link

openshift-ci bot commented Aug 20, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ibuziuk, kadel
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

@thepetk
Copy link
Contributor

thepetk commented Aug 20, 2025

/retest

@ibuziuk ibuziuk force-pushed the dotnet_deprecated branch from 6624046 to 98d81d2 Compare August 28, 2025 08:57
@openshift-ci openshift-ci bot removed the lgtm Looks good to me label Aug 28, 2025
Copy link

openshift-ci bot commented Aug 28, 2025

New changes are detected. LGTM label has been removed.

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented Aug 28, 2025

@thepetk could you please point me where the tests are expected to be updated?

@michael-valdron
Copy link
Member

@thepetk could you please point me where the tests are expected to be updated?

/test all

@ibuziuk Should be updated at the point of rebase, looking at the logs it appears to be another issue with AWS authentication. I'll try a retest of all.

@michael-valdron
Copy link
Member

/retest

1 similar comment
@michael-valdron
Copy link
Member

/retest

Copy link

openshift-ci bot commented Aug 28, 2025

@ibuziuk: The following test 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 98d81d2 link true /test v4.16-registry-test

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.

@michael-valdron
Copy link
Member

Seems persistent.. I'll have to open a ticket in the morning to see what's going on

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented Aug 29, 2025

@michael-valdron @thepetk thank you for the follow-up. Just to clarify, there is nothing required from my end at this point, right?

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.

5 participants