Skip to content

Update daily-builds.md - #9834

Merged
Rick-Anderson merged 3 commits into
mainfrom
Rick-Anderson-patch-1
Apr 8, 2025
Merged

Update daily-builds.md#9834
Rick-Anderson merged 3 commits into
mainfrom
Rick-Anderson-patch-1

Conversation

@Rick-Anderson

@Rick-Anderson Rick-Anderson commented Apr 6, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

image

@Rick-Anderson
Update daily-builds.md
9e95333 
This page has the most juice in searching for ".NET SDK daily builds"
Forgind
Forgind suggested changes Apr 6, 2025
View reviewed changes

@Forgind Forgind left a comment

Copy link
Copy Markdown

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
Rick-Anderson commented Apr 8, 2025
View reviewed changes
Comment thread daily-builds.md
@Rick-Anderson

Rick-Anderson commented Apr 8, 2025

Copy link
Copy Markdown
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
Forgind
Forgind approved these changes Apr 8, 2025
View reviewed changes

@Forgind Forgind left a comment

Copy link
Copy Markdown

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
@Rick-Anderson
Rick-Anderson deleted the Rick-Anderson-patch-1 branch April 8, 2025 21:55
@Forgind

Forgind commented Apr 8, 2025

Copy link
Copy Markdown

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

Reviewers

@richlander richlander Awaiting requested review from richlander
1 more reviewer
@Forgind Forgind Forgind approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Rick-Anderson @Forgind