Skip to content

Backport master changes to 5.x #710

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

Merged
merged 25 commits into from
Feb 14, 2020
Merged

Backport master changes to 5.x #710

merged 25 commits into from
Feb 14, 2020

Conversation

lukebakken
Copy link
Collaborator

I am reviewing all changes to master since the 5.1.2 release and backporting all that are appropriate for a 5.2.0 release.

michaelklishin and others added 2 commits February 11, 2020 13:12
@lukebakken lukebakken added this to the 5.2.0 milestone Feb 11, 2020
@lukebakken lukebakken self-assigned this Feb 11, 2020
@lukebakken lukebakken changed the base branch from master to 5.x February 11, 2020 21:19
@lukebakken
Copy link
Collaborator Author

@stebet - If I could ask a big favor. Could you please backport your changes in #687 to the lrb-master-backport-5.x branch? This process should work:

  • Update your fork of this repository (master and lrb-master-backport-5.x branches at least).
  • Create a branch based on lrb-master-backport-5.x
  • git cherry-pick -xm1 ebd7d215e6f9ce96a21f6f9bab119bb4097e568a
  • Fix merge conflicts! This is what trips me up every time.
  • Commit your branch, and open a PR using the lrb-master-backport-5.x branch as a base.

I really appreciate it.

@stebet
Copy link
Contributor

stebet commented Feb 12, 2020

Sure, I'll take a look at that tomorrow.

@lukebakken
Copy link
Collaborator Author

@stebet great thank you very much

@@ -71,7 +71,7 @@
</ItemGroup>

<ItemGroup>
<PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.0" PrivateAssets="All" />
<PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies.net451" Version="1.0.0" PrivateAssets="All" />
Copy link
Collaborator

Choose a reason for hiding this comment

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

What failure were you seeing? You shouldn't need to directly reference those sub packages. That should be correctly handled by referencing the Microsoft.NETFramework.ReferenceAssemblies package.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

On Linux and OS X builds -

https://gist.github.com/lukebakken/30d05fc5f03ee9ff47527e5d09864f26

This is the Vagrantfile that can bring up a Debian 10 VM with the same packages as our CI build - https://gist.github.com/lukebakken/676bb6d75e30aa5a0bc533f9af87a336

I have no idea what's up, just that these changes fix the builds! 🤷‍♂

Copy link
Collaborator

Choose a reason for hiding this comment

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

That doesn't really make sense though, because those packages would already be referenced with the original reference.

You would need to add Microsoft.NETFramework.ReferenceAssemblies to the WinRT project, but shouldn't need to reference a specific one directly like that.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I will give the WinRT suggestion a try. That's probably it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

e7578bf works. The reference is required in all of those .csproj files.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks for double-checking.

Copy link
Collaborator

Choose a reason for hiding this comment

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

If you're still having a problem with that change, post the build log failure, and I'll see if I can figure it out.

Ultimately I guess it does't matter, but it always bothers me when there's something weird going on without an explanation why. 😄

Copy link
Collaborator

Choose a reason for hiding this comment

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

Ah, should have refreshed before posting. Glad to see that solved it!

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

it always bothers me when there's something weird going on without an explanation why.

Me too, so thanks for checking. I don't have the time to dig into package / assembly / nuget issues and it's been long enough that I've been out of the .NET world that I'm quite rusty.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Things have also changed pretty dramatically with the introduction of PackageReferences and the new project system.

kjnilsson and others added 19 commits February 12, 2020 16:08
(cherry picked from commit 04518f1)
(cherry picked from commit db2f5a9)
(cherry picked from commit fca0136)
(cherry picked from commit 0ecf37d)
Use "dotnet build" command

(cherry picked from commit 5b6bf18)
Remove unused files

(cherry picked from commit 9e30a1b)
(cherry picked from commit 07c1936)
(cherry picked from commit 172ad8c)
Makes dotnet pack work. Kudos to @bording for figuring it out
in #700.

(cherry picked from commit 9b239f0)
Let operating system choose which TLS version to use

(cherry picked from commit 57cb199)
🔎 Sourcelink added!

(cherry picked from commit d81dd9d)
@lukebakken lukebakken force-pushed the lrb-master-backport-5.x branch from cba2b26 to e7578bf Compare February 13, 2020 00:09
@lukebakken lukebakken marked this pull request as ready for review February 14, 2020 16:05
@lukebakken lukebakken merged commit ad20306 into 5.x Feb 14, 2020
@lukebakken lukebakken deleted the lrb-master-backport-5.x branch February 14, 2020 16:24
@bording
Copy link
Collaborator

bording commented Feb 14, 2020

@lukebakken How closely did you look at the approval test changes in this branch to make sure there aren't breaking changes to types? That's my main concern with the backport process since breaking changes were okay when this stuff was merged into master.

@lukebakken
Copy link
Collaborator Author

Well I don't think there were changes to that but now you've got me double-checking...

lukebakken added a commit that referenced this pull request Feb 14, 2020
@lukebakken
Copy link
Collaborator Author

Well that's super, changes made it in that I didn't expect. Re-re-re-checking.

@lukebakken lukebakken restored the lrb-master-backport-5.x branch February 14, 2020 17:00
@lukebakken
Copy link
Collaborator Author

Maybe not. I see that there is a package added for the approval tests, and the expectation file, but the actual test itself isn't run. Going to address that because it will determine if API changes were made.

@stebet
Copy link
Contributor

stebet commented Feb 17, 2020

If any of the task changes caused API changes, let me know so I can fix them. There shouldn't be any need to change the API and cause breaking changes for them.

@lukebakken
Copy link
Collaborator Author

I'm getting the API approval test running in the 5.x branch and then I'll know for sure. Thanks for checking in @stebet

lukebakken added a commit that referenced this pull request Feb 20, 2020
Backport master changes to 5.x

(cherry picked from commit ad20306)
@lukebakken lukebakken deleted the lrb-master-backport-5.x branch February 20, 2020 22:44
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.

5 participants