Update Windows Server 2019 VM images — end of mainstream support
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- yaml
- Domain
- ci-cd, operating-systems
Research direction
Read build/.night-build.yml and build/.outer-loop-build.yml, then compare their VM image settings with the completed tracking entries in .vsts-dotnet-ci.yml and build/codecoverage-ci.yml. Update the two remaining Windows Server 2019 references to Windows Server 2022 and confirm both checklist items are complete.
Written by the indexing model from the issue text.
Description
An org-wide audit of the dotnet org found references to Windows Server 2019 VM images. Windows Server 2019 ended mainstream support in January 2024.
Part of .NET OS Support Tracking. See also: dotnet/runtime#125690, dotnet/dotnet-buildtools-prereqs-docker#1605.
Tracking
-
.vsts-dotnet-ci.yml—1es-windows-2019-open→1es-windows-2022-open -
build/codecoverage-ci.yml—1es-windows-2019-open→1es-windows-2022-open -
build/.night-build.yml—vmImage: windows-2019→vmImage: windows-2022 -
build/.outer-loop-build.yml—vmImage: windows-2019→vmImage: windows-2022
Details
This issue was generated by GitHub Copilot CLI v1.0.7 via the update-supported-os skill.
- Dominant language
- C#
- Stars
- 9.4k
- Forks
- 2k
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/machinelearning
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
dotnet/machinelearning#7751 · 1 comment ·
Maintainers usually reply within 2 days
-
BertTokenizer merges words separated only by `\n`, `\t` or `\r`Possibly taken @rosebyte claimed this 9 days ago. Openarea-Tokenizers green
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dotnet/machinelearning#7724 · 2 comments · 1 assignee ·
Maintainers usually reply within 2 days
-
area-TimeSeries documentation untriaged
Difficulty 1/5 Under an hour Newbie friendliness 90/100
dotnet/machinelearning#7205 ·
Maintainers usually reply within 2 days
-
Exception specification is missingPossibly taken @vejbomar claimed this 3 days ago. Openarea-DataFrame documentation
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
dotnet/machinelearning#6898 ·
Maintainers usually reply within 2 days
-
area-ONNX documentation Priority:3
Difficulty 1/5 Under an hour Newbie friendliness 88/100
dotnet/machinelearning#5894 · 1 comment ·
Maintainers usually reply within 2 days
All issues in dotnet/machinelearning
Similar issues
-
area/navigationview 🧭 difficulty/starter 🚀 good first issue kind/bug platform/all project/navigation-lifecycle 🧬 triage/untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
unoplatform/uno#24925 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DamianEdwards/ghcp-spend-tray#39 ·
Maintainers usually reply within 1 day
-
copilot documentation
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
[Rust][Flaky Test] multiple_deadlines_fire_in_order asserts a wall-clock gap instead of firing orderOpenCI/CD ⚒️ Flaky-tests 🐦
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
valkey-io/valkey-glide#7255 ·
Maintainers usually reply within 3 days
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
unoplatform/Uno.Core#99 ·