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 resourceManagement.yml #77948

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update resourceManagement.yml #77948

wants to merge 1 commit into from

Conversation

jaredpar
Copy link
Member

@jaredpar jaredpar commented Apr 1, 2025

Policy change to help participate in the SDK breaking changes work

https://github.com/dotnet/sdk/blob/main/documentation/project-docs/breaking-change-guidelines.md

@jaredpar jaredpar requested a review from a team as a code owner April 1, 2025 17:35
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Apr 1, 2025
@jaredpar
Copy link
Member Author

jaredpar commented Apr 1, 2025

@dotnet/roslyn-infrastructure PTAL

When you commit this breaking change:


1. [ ] Create and link to this PR and the issue a matching issue in the dotnet/docs repo using the [breaking change documentation template](https://aka.ms/dotnet/docs/new-breaking-change-issue), then remove this `needs-breaking-change-doc-created` label.
Copy link
Member

Choose a reason for hiding this comment

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

Do we really want to add doc to dotnet/docs? Shouldn't we continue using our breaking change docs?

Copy link
Member Author

Choose a reason for hiding this comment

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

@baronfel this was the recommendation of the sdk breaking change doc.


1. [ ] Create and link to this PR and the issue a matching issue in the dotnet/docs repo using the [breaking change documentation template](https://aka.ms/dotnet/docs/new-breaking-change-issue), then remove this `needs-breaking-change-doc-created` label.

2. [ ] Ask a committer to mail the `.NET SDK Breaking Change Notification` email list.
Copy link
Member

Choose a reason for hiding this comment

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

Do we want to be doing this as well? Isn't that meant only for sdk repo breaking changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants