Skip to content

Conversation

@magiudev
Copy link
Contributor

@magiudev magiudev commented Sep 29, 2024

Corrected a typo in the list featured in the .NET Implementations article

Fixes #42750


Internal previews

📄 File 🔗 Preview link
docs/fundamentals/implementations.md docs/fundamentals/implementations

@magiudev magiudev requested a review from a team as a code owner September 29, 2024 12:08
@dotnetrepoman dotnetrepoman bot added this to the September 2024 milestone Sep 29, 2024
@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates PR is created by someone from the .NET community. label Sep 29, 2024
@gewarren
Copy link
Contributor

gewarren commented Oct 4, 2024

This is intentional, as .NET 5 is out of support.

@gewarren gewarren closed this Oct 4, 2024
@dotnet-policy-service dotnet-policy-service bot added the okr-quality Content-quality KR: Concerns article defects (bugs), freshness, or build warnings. label Oct 4, 2024
@magiudev
Copy link
Contributor Author

magiudev commented Oct 5, 2024

@gewarren, may I ask you to elaborate on this, please? It doesn't make sense that the item in the list doesn't match the title, as I explained in the issue. It seems to me that either the item is wrong or the title is wrong.

I have found multiple references where .NET 5 is grouped with its successive versions:

Screenshot 2024-10-06 at 2 32 14 PM

Even if .NET 5 is out of support it is the first version of that specific .NET implementation

@gewarren gewarren reopened this Oct 7, 2024
@gewarren gewarren enabled auto-merge (squash) October 7, 2024 16:07
@gewarren gewarren merged commit 747860e into dotnet:main Oct 7, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-contribution Indicates PR is created by someone from the .NET community. dotnet-fundamentals/svc okr-quality Content-quality KR: Concerns article defects (bugs), freshness, or build warnings.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Typo in the .NET Implementations article

2 participants