Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Update daily-builds.md#9834

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

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

Update daily-builds.md#9834

Rick-Anderson merged 3 commits intomainfromRick-Anderson-patch-1
Apr 8, 2025

Conversation

@Rick-Anderson
Copy link
Contributor

@Rick-AndersonRick-Anderson commentedApr 6, 2025
edited
Loading

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

@ForgindForgind 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
ContributorAuthor

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.

Copy link

@ForgindForgind 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-AndersonRick-Anderson merged commit0363daf intomainApr 8, 2025
4 checks passed
@Rick-AndersonRick-Anderson deleted the Rick-Anderson-patch-1 branchApril 8, 2025 21:55
@Forgind
Copy link

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 toupdate 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 freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@richlanderrichlanderAwaiting requested review from richlander

1 more reviewer

@ForgindForgindForgind 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.

3 participants

@Rick-Anderson@Forgind

[8]ページ先頭

©2009-2025 Movatter.jp