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

Merge release/2.0.0 into master #1602

Merged
merged 54 commits into from
Sep 25, 2017
Merged

Merge release/2.0.0 into master #1602

merged 54 commits into from
Sep 25, 2017

Conversation

livarcocc
Copy link
Contributor

@dotnet/dotnet-cli

nugetlurker and others added 30 commits July 23, 2017 16:23
Insert NuGet Build 4.3.0-rtm-4324 into sdk
Setting RestoreAdditionalProjectFallbackFoldersExcludes when the TFM is 1.x to prevent fallback folders from being used in that case. Note that NuGet will have to do the aggregation of these properties in order for this to work.
Adds fallback folder for full framework projects.
LOC CHECKIN | sdk-release/2.0.0 | 20170726
Free metadata reader and assembly after reading metadata
Update error message text when 2.0 SDK is required to build a project
Insert NuGet Build 4.3.0-rtm-4382 into sdk
Revert "Update version to 2.0.2-vspre"
Update version to 2.0.2-vspre and update NuGet
Bump default versions for self-contained apps
Insert NuGet Build 4.4.0-preview1-4434 into sdk
nguerrera and others added 23 commits September 11, 2017 16:32
Revert self-contained implicit versions to 1.0.5/1.1.2/2.0.0
This is already set in the build script, but setting it here will apply to scenarios such as running tests from VS
Update support libraries to those that are only lib.
Use correct target path for runtimeTargets items when resolving conflicts
Insert NuGet Build 4.4.0-preview3-4475 into sdk
* release/2.0-vs:
  Update CLI version
  Fix test issue with path separator character
  Fix perf regression with setting DestinationSubPath on items for conflict resolution
  Add build/test environment scripts
  Fix satellite assembly conflict resolution when targeting .NET Core
  Take locale portion of target path for satellite assemblies into account in conflict resolution
  Add comment clarifying test expectation
  Change log verbosity to normal when checking whether projects encounter conflicts
  Use correct target path for runtimeTargets items when resolving conflicts
  Disable multilevel lookup for Tests
  Disable multilevel lookup in build/test to prevent accidental machine dependencies
  Insert NuGet Build 4.4.0-preview3-4475 into sdk
  Update support libraries to those that are only lib.
  Update DotnetCLIVersion
  fix intermediate nuspec path
  Insert NuGet Build 4.4.0-preview1-4434 into sdk
  Insert NuGet Build 4.4.0-preview1-4365 and corresponding CLI version into SDK
Merge release/2.0-vs into release/2.0.0
* release/2.0.0: (33 commits)
  Update CLI version
  Fix test issue with path separator character
  Fix perf regression with setting DestinationSubPath on items for conflict resolution
  Add build/test environment scripts
  Fix satellite assembly conflict resolution when targeting .NET Core
  Take locale portion of target path for satellite assemblies into account in conflict resolution
  Add comment clarifying test expectation
  Change log verbosity to normal when checking whether projects encounter conflicts
  Use correct target path for runtimeTargets items when resolving conflicts
  Disable multilevel lookup for Tests
  Disable multilevel lookup in build/test to prevent accidental machine dependencies
  Insert NuGet Build 4.4.0-preview3-4475 into sdk
  Update support libraries to those that are only lib.
  Revert self-contained implicit versions to 1.0.5/1.1.2/2.0.0
  Update DotnetCLIVersion
  fix intermediate nuspec path
  Insert NuGet Build 4.4.0-preview1-4434 into sdk
  Bump default versions for self-contained apps
  Disable multilevel lookup in build/test to prevent accidental machine dependencies
  Revert "Update version to 2.0.2-vspre"
  ...
@dsplaisted
Copy link
Member

dsplaisted commented Sep 25, 2017 via email

@livarcocc
Copy link
Contributor Author

@dsplaisted did that on Friday.

@@ -1 +1 @@
2.1.0-preview1-007041
2.0.2-vspre-006963
Copy link
Member

Choose a reason for hiding this comment

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

This means we're no longer using a master version of the SDK with the master version of the CLI? Shouldn't we merge release/2.0-vs and release/2.0.0 into master in the SDK, then use that version of the SDK here? Or can we not do that right now because signing is down?

Copy link
Contributor

Choose a reason for hiding this comment

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

Or can we not do that right now because signing is down?

I think that's exactly the issue. @livarcocc mentioned as much in standup today and note that f1fe4af does this deliberately post-merge.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, signing.

@livarcocc livarcocc merged commit ac2507b into master Sep 25, 2017
@livarcocc livarcocc deleted the merge_release200 branch September 25, 2017 21:04
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.

7 participants