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.10 #6031

Merged
merged 2 commits into from
Jan 19, 2021
Merged

Update branding for 16.10 #6031

merged 2 commits into from
Jan 19, 2021

Conversation

Forgind
Copy link
Member

@Forgind Forgind commented Jan 13, 2021

Not until vs16.9 is brought up-to-date.

Also, for the binding redirects/code bases, is it a string comparison, a version comparison, or a number comparison? Wondering if it would interpret 16.9 as greater or less than 16.10.


[![Build Status](https://dev.azure.com/dnceng/public/_apis/build/status/Microsoft/msbuild/msbuild-pr?branchName=master)](https://dev.azure.com/dnceng/public/_build/latest?definitionId=86&branchName=master)

We have forked for MSBuild 16.8 in the branch [`vs16.8`](https://github.com/Microsoft/msbuild/tree/vs16.8). Changes to that branch need special approval.
We have forked for MSBuild 16.9 in the branch [`vs16.9`](https://github.com/Microsoft/msbuild/tree/vs16.9). Changes to that branch need special approval.
Copy link
Member

Choose a reason for hiding this comment

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

I think we can finally remove the 16.0 info here 🎉

@Forgind Forgind added the merge-when-branch-open PRs that are approved, except that there is a problem that means we are not merging stuff right now. label Jan 15, 2021
@Forgind Forgind merged commit 7814dc4 into dotnet:master Jan 19, 2021
@Forgind Forgind deleted the 16.10-branding branch January 19, 2021 23:06
chsienki pushed a commit to chsienki/msbuild that referenced this pull request Jan 28, 2021
benvillalobos added a commit that referenced this pull request Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge-when-branch-open PRs that are approved, except that there is a problem that means we are not merging stuff right now.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants