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 branding for 16.11 #6407

Merged
merged 1 commit into from
May 4, 2021
Merged

Update branding for 16.11 #6407

merged 1 commit into from
May 4, 2021

Conversation

ladipro
Copy link
Member

@ladipro ladipro commented May 4, 2021

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

Copy link
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

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

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.

@ladipro ladipro merged commit e9fd69a into dotnet:vs16.11 May 4, 2021
@ladipro ladipro deleted the 16.11-branding branch May 4, 2021 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants