Update branding for 16.11#6407
Merged
ladipro merged 1 commit intodotnet:vs16.11from May 4, 2021
Merged
Conversation
rainersigwald
approved these changes
May 4, 2021
Member
rainersigwald
left a comment
rainersigwald
left a comment
There was a problem hiding this comment.
Looks like the VS branch is already created internally, too, so we should be able to insert. Right now our insertion automation isn't smart enough to figure out the right destination branch and it's hardcoded to 16.10 (or maybe even 16.9, not sure if we've updated it yet). I'd leave it at rel/d16.10 until that's released and we can manually trigger insertion jobs for this 16.11 branch to rel/d16.11.
Unless of course you want to fix the automation but that seems probably not worth it cost/benefit wise.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
While mainline development is now focusing on 17.0, we want to have the 16.11 branch ready in case we end up contributing.
Changes Made
Setting up a branch for MSBuild inserted into Visual Studio 16.11.
Testing
Grepped the tree for other occurrences of 16.10.
Notes