Skip to content
This repository has been archived by the owner on Apr 20, 2023. It is now read-only.

Updating the branding of the CLI to 2.1.100 #8389

Merged

Conversation

livarcocc
Copy link

This updates the branding of the CLI according to our new version scheme.

cc @KathleenDollard

@livarcocc livarcocc requested a review from a team January 12, 2018 23:39
@@ -1,6 +1,6 @@
<Project>
<PropertyGroup>
<Channel>release/15.5</Channel>
<BranchName>release/15.5</BranchName>
<Channel>release/2.0</Channel>

This comment was marked as spam.

This comment was marked as spam.

@livarcocc
Copy link
Author

@dotnet-bot Test this please.

@mmitche
Copy link
Member

mmitche commented Jan 13, 2018

@dotnet-bot test this please

1 similar comment
@mmitche
Copy link
Member

mmitche commented Jan 13, 2018

@dotnet-bot test this please

…se/2.0 if necessary, but LTS is always updated every time we release.
…i-1 into update_branding_for_2_1_100

* 'update_branding_for_2_1_100' of github.com:livarcocc/cli-1:
  MSBuild 15.6.44
@livarcocc livarcocc merged commit 25de769 into dotnet:release/2.1.1xx Jan 16, 2018
@livarcocc livarcocc deleted the update_branding_for_2_1_100 branch January 16, 2018 19:54
@dasMulli
Copy link

@livarcocc @KathleenDollard is there any explaining doc on the versioning scheme? After discussion on https://github.com/dotnet/cli/issues/8042 and https://github.com/dotnet/designs/issues/2 I'd really appreciate a few words on this 😄

@KathleenDollard
Copy link

This change is explained here: dotnet/designs#29

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants