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

Required changes for 3.0.0 preview3 #112

Merged
merged 14 commits into from
Feb 21, 2019
Merged

Required changes for 3.0.0 preview3 #112

merged 14 commits into from
Feb 21, 2019

Conversation

JunTaoLuo
Copy link
Contributor

I noticed a few changes in preview3 and updated our code accordingly.

Copy link
Contributor

@jtattermusch jtattermusch left a comment

Choose a reason for hiding this comment

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

approved, but we need to figure out the question of depending on daily build vs. depending on a released version.
We definitely need a test that makes sure that everything is working against the latest released version (preview2 for now, preview3 soon). I'm not sure about the importance of testing against the unreleased version of .NET core - that depends on how often we will need access to new APIs and fixes (hopefully not often because the thing needs to work for users with preview3 anyway?). If we need both, we should have two tests.

@JunTaoLuo
Copy link
Contributor Author

cc @halter73

@JunTaoLuo JunTaoLuo merged commit c7ca9ce into grpc:master Feb 21, 2019
@JunTaoLuo JunTaoLuo deleted the preview3-fixes branch February 21, 2019 01:45
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