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 daily-builds.md #9834

Merged
merged 3 commits into from
Apr 8, 2025
Merged

Update daily-builds.md #9834

merged 3 commits into from
Apr 8, 2025

Conversation

Rick-Anderson
Copy link
Contributor

@Rick-Anderson Rick-Anderson commented Apr 6, 2025

This page has the most juice in searching for ".NET SDK daily builds"

image

This page has the most juice in searching for ".NET SDK daily builds"
Copy link
Member

@Forgind Forgind left a comment

Choose a reason for hiding this comment

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

I don't think that has all the same information, though, so I don't think you can just refer to that.

@Rick-Anderson
Copy link
Contributor Author

I don't think that has all the same information, though, so I don't think you can just refer to that.

I restored that, but I don't see the value of listing .NET 8.0 a future release. I suggest deleting the future releases table and updating the servicing table.
.NET 6 & 7, listed in the servicing releases are out of support and no longer serviced.

@Rick-Anderson Rick-Anderson requested a review from Forgind April 8, 2025 21:51
Copy link
Member

@Forgind Forgind left a comment

Choose a reason for hiding this comment

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

This looks fine to me

@Rick-Anderson Rick-Anderson merged commit 0363daf into main Apr 8, 2025
4 checks passed
@Rick-Anderson Rick-Anderson deleted the Rick-Anderson-patch-1 branch April 8, 2025 21:55
@Forgind
Copy link
Member

Forgind commented Apr 8, 2025

I don't think that has all the same information, though, so I don't think you can just refer to that.

I restored that, but I don't see the value of listing .NET 8.0 a future release. I suggest deleting the future releases table and updating the servicing table. .NET 6 & 7, listed in the servicing releases are out of support and no longer serviced.

I think it'd be positive to update those to versions that actually haven't been released yet. As you said, .NET 7 isn't in support, and .NET 8 is already released. But we could say something similar with .NET 10 as a "future" release and .NET 8/9 as past releases still in support

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