Runtime: Infrastructure - Rollout (December 2020)

Created on 11 Nov 2020 · 5Comments · Source: dotnet/runtime

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 (12/7).

| Change | Impact | Assignee |
| --- | --- | --- |
| #44523 | Update the minimum and target version of the SDK to 5.0.100. | @ViktorHofer |
| #44973 | Remove the nested 'src' folder from the CoreCLR part of the repository. | @trylek |

Most helpful comment

IMO the why should be part of the PRs description and this table should only list the changes but not go into detail. Otherwise the table will always lack behind the data in the linked changes.

ViktorHofer on 11 Nov 2020

👍3

All 5 comments

Tagging subscribers to this area: @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue meta data

Issue content:	# 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 (12/7). \| Change \| Impact \| Assignee \| \| --- \| --- \| --- \| \| #44523 \| Update the minimum and target version of the SDK to 5.0.100. \| @ViktorHofer \| Archive November 2020 September 2020 July 2020 June 2020 May 2020 April 2020
Issue author:	ViktorHofer
Assignees:	ViktorHofer
Milestone:	[object Object]

msftbot[bot] on 11 Nov 2020

I wonder if it might be useful to have a column for "why"? In this case, it's so that we are using the supported, GA SDK.

danmosemsft on 11 Nov 2020

IMO the why should be part of the PRs description and this table should only list the changes but not go into detail. Otherwise the table will always lack behind the data in the linked changes.

ViktorHofer on 11 Nov 2020

👍3

Why update to 5.0.100 and not 6.0 to start preparing for January preview?