-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Infrastructure - Rollout (June 2021) #53411
Comments
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsOverviewWe use this issue to announce planned Infrastructure changes that will impact the developer workflow in
Archive
|
dotnet-issue-labeler
bot
added
the
untriaged
New issue has not been triaged by the area owner
label
May 28, 2021
ViktorHofer
removed
the
untriaged
New issue has not been triaged by the area owner
label
May 28, 2021
ViktorHofer
added a commit
that referenced
this issue
Jun 7, 2021
Update the minimum and target version of the SDK to 6.0 Preview 4. Part of #53411
ViktorHofer
added a commit
that referenced
this issue
Jun 11, 2021
* Update dotnet SDK to 6.0 Preview 4 Update the minimum and target version of the SDK to 6.0 Preview 4. Part of #53411 * Switch to using eng/targetingpacks.targets for redirecting runtime pack location in src/mono/sample * Fix binder tracing tests * Set UseMonoRuntime property so the dotnet SDK can pull the mono runtime packs This is necessary after the changes from dotnet/sdk#16909. * Move UseMonoRuntimeProperty and set it to false in coreclr Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> Co-authored-by: Elinor Fung <elfung@microsoft.com>
ghost
locked as resolved and limited conversation to collaborators
Jul 14, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Overview
We use this issue to announce planned Infrastructure changes that will impact the developer workflow in
dotnet/runtime
. Changes will be merged on the first Monday of the month (6/7).Archive
The text was updated successfully, but these errors were encountered: