Skip to content

Release 17.5 #8246

New issue
New issue
Closed
Closed
Release 17.5#8246
Labels
triaged
@rainersigwald

Description

@rainersigwald
rainersigwald
opened on Dec 15, 2022
  • When VS main snaps to 17.6, create vs17.5 branch
  • Create darc channel for VS 17.6 if it doesn't already exist
    darc add-channel --name "VS 17.6"
  • Ping internal "First Responders" Teams channel to get the new channel made available as a promotion target
  • Associate the next release branch with the next release channel
    darc add-default-channel --channel "VS 17.6" --branch vs17.6 --repo https://github.com/dotnet/msbuild
  • Remove the main to old release channel default channel
    darc delete-default-channel --repo https://github.com/dotnet/msbuild --branch main --channel "VS 17.5"
  • Associate the main branch with the next release channel
    darc add-default-channel --channel "VS 17.6" --branch main --repo https://github.com/dotnet/msbuild
  • Check subscriptions for the current channel VS 17.5 and update as necessary (for instance, SDK's main branch should usually be updated, whereas release branches often should not be
    darc get-subscriptions --exact --source-repo https://github.com/dotnet/msbuild --channel "VS 17.5"
    Update channel VS 17.5 to VS 17.6 for the sdk main subscription
    darc update-subscription --id 5480c5ca-4fa6-4d8a-1987-08d9d606f30d
  • Ensure that the current release channel VS 17.5 is associated with the correct release branch
    darc get-default-channels --source-repo https://github.com/dotnet/msbuild --branch vs17.5
  • Fast-forward merge the correct commit (the one that is currently inserted to VS main) to the vs17.5 branch
    git push upstream 797fd829a374a880f63fd4eea4ea6990404c48f4:refs/heads/vs17.5
  • Update the branch merge flow in dotnet/versions to have the currently-in-servicing branches (extend Automate MSBuild's merge chain versions#867)
  • Fix OptProf data flow for the new vs17.5 branch
  • Update the release-branch insertion release definition to have InsertTargetBranch rel/d17.5.
  • Prepare final branding PR for vs17.5 but ⚠️ DO NOT MERGE IT YET ⚠️
  • Create 17.6 branding PR, including public API baseline package version change (see Public api analyzer change #8116 (comment))
  • Merge 17.6 branding PR
  • Prepare QB-mode bug for final branding insertion in internal VS repo
  • Update internal "create VS PR for insertion" release to point to the new VS release branch by default
  • Merge final branding to vs17.5 branch
  • Get QB approval
  • Merge to VS
  • ASAP after release, push packages to nuget.org (not currently automated, contact dnceng)
  • Update main subscriptions to the new channel (this can be done after release)
    darc get-subscriptions --exact --target-repo https://github.com/dotnet/msbuild --target-branch main
  • Create the 17.5 release
  • Update the PackageValidationBaselineVersion to the latest released version (17.5.0)

Metadata

Metadata

Assignees

No one assigned

    Labels

    triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions