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

Retire change wave 17.4 #9543

Closed
wants to merge 1 commit into from

Conversation

rainersigwald
Copy link
Member

Its time has come, per the documented schedule.

Its time has come, per the documented schedule.
@rainersigwald
Copy link
Member Author

Question for @baronfel and @marcpopMSFT: does the newer "try to stack breaking changes on .NET Core releases" policy imply that we should instead require all stale changewaves in the X.0.100 release, instead of an even MSBuild release as we have been doing?

@marcpopMSFT
Copy link
Member

You mean basically retire the change waves once a year in November instead of every 6 months? I guess retiring a change wave is breaking so maybe that makes sense? Would we retire two waves each year?

Comment on lines -462 to -464
MSBuildEventSource.Log.SdkResolverServiceInitializeStart();
_resolversList = _sdkResolverLoader.LoadAllResolvers(location);
MSBuildEventSource.Log.SdkResolverServiceInitializeStop(_resolversList.Count);
Copy link
Member

Choose a reason for hiding this comment

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

nit: LoadAllResolvers is now unused in product code and so are the two event source calls. It looks like LoadResolversFromManifest and LoadResolvers become transitively dead as well.

@rainersigwald
Copy link
Member Author

Closing to wait for 9.0

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

Successfully merging this pull request may close these issues.

5 participants