.NET Release - 6.0 Preview 4

[mthalman]

.NET Release

Release Versions

The set of .NET versions that are being released as a unit.

• 6.0.0-preview.4.21253.7/6.0.100-preview.4.21255.9

1. Main Branch Tasks

1. • Merge appropriate commits from nightly branch. Things to check:
     • New/EOL distro
     • Infrastructure changes
     • PowerShell version (Update PowerShell to v7.2.0-preview.5 #2746)
     • Check for additional changes by diffing the main and nightly branches
     • Update SDK image first run handling #2710
     • Set console formatter to JSON in ASP.NET Core images #2748
2. • Check whether a change has been made to a Dockerfile that is shared by multiple .NET versions. If a change has been made and the .NET versions that share that file are not being released at the same time, define a separate Dockerfile to isolate the change to the .NET version that's being released. Conversely, after a shared Dockerfile has diverged in such a way, it should be combined again into a shared Dockerfile when the other other .NET version is released. Shared Dockerfiles to check:
     • 3.1 runtime-deps shared with 5.0 and 6.0
3. • Wait for .NET archive files (.zip, .tar.gz) to be available at blob storage location
4. • Run update-dependencies tool to update all the necessary files to reflect the specified .NET versions (run this command for each version being released):
     • dotnet run --project .\eng\update-dependencies\update-dependencies.csproj 6.0 --product-version sdk=6.0.100-preview.4.21255.9 --product-version runtime=6.0.0-preview.4.21253.7 --product-version aspnet=6.0.0-preview.4.21253.5
5. • Inspect generated changes for correctness
6. • Commit generated changes
7. • Create PR
8. • Get PR signoff
9. • Merge PR
10. • Wait for changes to be mirrored to internal dotnet-docker repo (internal MSFT link)

11. • Build images - Queue build stage of dotnet-docker pipeline (internal MSFT link) with variables:

      All releases:

       stages: build
      

      Preview release (exclude 3.1 if separate runtime-deps Dockerfiles were defined):

       imageBuilder.pathArgs: --path 'src/*/3.1/*' --path 'src/*/5.0/*' --path 'src/*/6.0/*' --path 'src/monitor/*'
      

12. • Wait for NuGet packages to be published during release tic-toc

13. • Test and publish images - Queue build of dotnet-docker pipeline (internal MSFT link) with variables:

      All releases:

       stages: test;publish
       sourceBuildId: <Build ID from the build stage>
      

      Preview release (exclude 3.1 if separate runtime-deps Dockerfiles were defined):

       imageBuilder.pathArgs: --path 'src/*/3.1/*' --path 'src/*/5.0/*' --path 'src/*/6.0/*' --path 'src/monitor/*'
      

14. • Confirm READMEs have been updated in Docker Hub