-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Merge 17.0-vs-deps to 17.0 #57156
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
Merge 17.0-vs-deps to 17.0 #57156
Conversation
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
Merge main to main-vs-deps
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
Merge main to main-vs-deps
Merge main to main-vs-deps
Merge main to main-vs-deps
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
Merge main to main-vs-deps
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
Merge main to main-vs-deps
Merge main to main-vs-deps
Merge main to main-vs-deps
Merge main to main-vs-deps
Merge main to main-vs-deps
Merge main to main-vs-deps
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
Merge main to main-vs-deps
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
Merge main to main-vs-deps
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
Merge main to main-vs-deps
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
Merge main to main-vs-deps
Merge main to main-vs-deps
…-deps-to-main-vs-deps Merge release/dev17.0-vs-deps to main-vs-deps
Merge main to main-vs-deps
Merge main to main-vs-deps
… Build ID 1395771
… Build ID 1395758
… Build ID 1395758
… Build ID 1395771
… Build ID 1395771
…90-a203-3b68c4a3defd Localized file check-in by OneLocBuild Task: Build definition ID 327: Build ID 1395644
…b4-92c3-1665bb4f4740 Localized file check-in by OneLocBuild Task: Build definition ID 327: Build ID 1395771
…-release/dev17.0-vs-deps Merge release/dev17.0 to release/dev17.0-vs-deps
…-release/dev17.0-vs-deps Merge release/dev17.0 to release/dev17.0-vs-deps
…-release/dev17.0-vs-deps Merge release/dev17.0 to release/dev17.0-vs-deps
…2d-8273-281fa1024c0f Localized file check-in by OneLocBuild Task: Build definition ID 327: Build ID 1395758
…-release/dev17.0-vs-deps Merge release/dev17.0 to release/dev17.0-vs-deps
…-release/dev17.0-vs-deps Merge release/dev17.0 to release/dev17.0-vs-deps
Co-authored-by: Sam Harwell <Sam.Harwell@microsoft.com>
…-release/dev17.0-vs-deps Merge release/dev17.0 to release/dev17.0-vs-deps
sharwell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just delete the release/dev17.0 branch, like we've done for all former releases when the vs-deps backward merge occurred?
|
Some examples of where this has been done in the past for release branches: I think deleting the -vs-deps branch is preferred to deleting the non-vs-deps branch because we end up with simpler branch names. It also makes the process of flowing these -vs-deps updates downstream to later releases a little more clear because it fits with our codeflow conventions. |

No description provided.