New Windows Release - 20H2

[mthalman]

New Windows Release

Windows version: 20H2

Prep Tasks

1. • Ensure a "New Windows Release" issue exists for docker-tools repo
2. • Copy the Dockerfiles of the most recent published Windows version for 3.5 and 4.8 Dockerkfiles and place them in a version-specific folder under their respective variants (runtime, sdk, aspnet, wcf)
3. • Modify the Dockerfiles as appropriate for any specific changes related to the new Windows version
     • The 3.5/runtime Dockerfile will need to have the Apply latest patch section removed since there is no patch to apply for a new Windows version
4. • Update manifest.json to reference the new set of Dockerfiles with the appropriate tags
5. • Update manifest.samples.json to include the new Windows version for each of the samples
6. • Update the test data for each of the test classes to include the new Windows version
7. • Look up the recommended latest NuGet CLI version and update the nuget-info.json file to associate that NuGet version with the new version of Windows
8. • Run the update-dependencies tool to update all the necessary files:
     • dotnet run --project .\eng\update-dependencies
9. • Inspect generated changes for correctness
10. • Test the images
      1. • Create a local VM of the new Windows version
      2. • Clone this repo with the above changes onto the VM
      3. • Run .\build-and-test.ps1 -OS windowsservercore-<VERSION> to build and test your changes
11. • Revert any modifications that were made to the 3.5/runtime Dockerfile to support local testing due to the lack of the https://dotnetbinaries.blob.core.windows.net/dockerassets/microsoft-windows.netfx3-.zip file.
12. • Commit generated changes
13. • Create PR
14. • Get PR signoff. Don't merge PR to master.

Release Day Tasks

1. • Create a `microsoft-windows.netfx3-.zip file containing the .NET Fx 3.5 cab installer file and upload it to the blob storage location.
2. • Ensure all build agent scale sets have the appropriate number of machines allocated for a build
3. • Merge any pending PRs or commits from dev branch:
     • <placeholder link>
4. • Look up the latest NuGet CLI versions and update the nuget-info.json file with the latest patch of each major/minor version listed in the file.
5. • Run the update-dependencies tool to update all the necessary files:
     • dotnet run --project .\eng\update-dependencies --datestamp-all <YYYYMMDD>
6. • Inspect generated changes for correctness
7. • Commit generated changes
8. • Create PR
9. • Get PR signoff
10. • Merge PR
11. • Wait for changes to be mirrored to internal dotnet-framework-docker repo (internal MSFT link)

12. • Run the Get-BaseImageStatus.ps1 script and wait until the Windows images have been updated as part of the Windows Patch Tuesday release process. This script will display when the dependent Windows images were last updated. Wait until all the images show that they have been recently updated. "Recently updated" amounts to be having been updated within the past week or so; images from a month ago should be considered to be the old version.

       ./eng/common/Get-BaseImageStatus.ps1 -Continuous
      

13. • Queue build of dotnet-framework-docker pipeline (internal MSFT link). Path args: src/*/windowsservercore-2009
14. • Confirm images have been ingested by MCR
15. • Confirm READMEs have been updated in Docker Hub for microsoft-dotnet-framework
16. • Confirm build for dotnet-docker-framework-samples (internal MSFT link) was queued. This will be queued automatically by dotnet-docker-tools-check-base-image-updates when it detects that the product images have been updated (detection runs on a schedule). Alternatively, you can manually queue the samples build.
17. • Confirm sample images have been ingested by MCR
18. • Confirm Last Modified field has been updated in Docker Hub for microsoft-dotnet-framework-samples
19. • Deallocate any extra scale set build agent machines if necessary
20. • Create an announcement (example: Windows Server, version 1909)

[ChrisMcKee]

Will this release contain the size reductions shown in https://devblogs.microsoft.com/dotnet/we-made-windows-server-core-container-images-40-smaller/ by any chance?

[MichaelSimons]

Will this release contain the size reductions shown in https://devblogs.microsoft.com/dotnet/we-made-windows-server-core-container-images-40-smaller/ by any chance?

@ChrisMcKee - They were already released as part of 20H1.

[ChrisMcKee]

Will this release contain the size reductions shown in https://devblogs.microsoft.com/dotnet/we-made-windows-server-core-container-images-40-smaller/ by any chance?

@ChrisMcKee - They were already released as part of 20H1.

Ah right I was looking at these stats

But the image for 4.8 runtime was 6.84gb, so I assumed it hadn't gone out.
I've probably missed something in the docs.

[MichaelSimons]

The current mcr.microsoft.com/dotnet/framework/runtime:4.8-windowsservercore-2004 image is 5.22 GB. Unfortunately this has grown substantially because of the Windows OS patching layer which is currently 1.54 GB. The patching layer is part of the windowsservercore base OS image.

> docker history mcr.microsoft.com/dotnet/framework/runtime:4.8-windowsservercore-2004
IMAGE               CREATED             CREATED BY                                      SIZE                COMMENT
d01395ea8dc2        4 weeks ago         cmd /S /C \Windows\Microsoft.NET\Framework64…   369MB
<missing>           4 weeks ago         cmd /S /C #(nop)  ENV DOTNET_RUNNING_IN_CONT…   41kB
<missing>           4 weeks ago         cmd /S /C curl -fSLo patch.msu http://downlo…   674MB
<missing>           5 weeks ago         Install update 2004-amd64                       1.54GB
<missing>           10 months ago       Apply image 2004-RTM-amd64                      2.65GB

[ChrisMcKee]

@MichaelSimons Thanks; I'd pulled an earlier insider one and couldn't work out where all the extra disk was being used 👍
Constantly chasing the dream of not having to push multiple gigs into ACR 😉

Thanks again; at least I know I'm not doing something wrong 😁