Skip to content

Latest commit

 

History

History
46 lines (29 loc) · 2.48 KB

release-activity.md

File metadata and controls

46 lines (29 loc) · 2.48 KB

Runtime release procedures

Milestone releases (dotnet/winforms + dotnet/windowsdesktop)

  1. Merge any outstanding PRs, if necessary

  2. Ensure the HEAD of the main branch builds successfully and all tests pass

  3. Publish any unpublished API - run .\eng\ApiCompatibility\mark-shipped.cmd

  4. Commit and wait for a successful build

  5. (Milestone releases) Create "release/X.Y-qwe" branch (e.g. release/6.0-preview5) and push it into the main public trunk and the internal trunk. Wait for both build successfully.

  1. Disable loc on "release/X.Y-qwe" branch (e.g.: #6753)

  2. Switch back to the main branch

  3. Update the Service Fabric bot with the new release label in .\github\fabricbot.json. Refer to .\docs\infra\automation.md, if have questions.

  4. Update the branding (e.g.: https://github.com/dotnet/winforms/commit/719b2112778ffd1e7ded559ea2736b4011428117)

  5. Commit and wait for a successful build.

  6. Create new milestone for the new release before updating following bot service.

  7. Move work items to this new milestone if they were on previous milestone and close the previous milestone.

  8. Update necessary reports with the progress

  9. If you are responsible for dotnet/windowsdesktop repo, make sure you change the branding there too.

Servicing releases (dotnet/winforms + dotnet/windowsdesktop)

NET Servicing - Overview (azure.com)

  1. Merge internal servicing branch (i.e. internal/internal/release/*) into the public branch, if necessary.

  2. Update the branding (e.g.: https://github.com/dotnet/winforms/commit/480bd703c5af93b9e23dc7435c6029d685be7097)

  3. Commit and wait for a successful build.

  4. Ensure the HEAD of the servicing branch builds successfully and all tests pass

  5. Update dotnet/installer with the released version (e.g.: https://github.com/dotnet/installer/commit/34ed90f436809631e254b9e15628cbcad7307629)

  6. Create a new milestone.

  7. Close the current milestone on the GitHub, ensuring all open issues/PRs are either closed or bumped to the following milestone

  8. Merge any outstanding PRs, if necessary