AFTER 18.3 Activities

[YuliiaKovalova]

ASAP On/After GA:

Timing based on the (Microsoft-internal) release schedule.

• Push packages to nuget.org (not currently automated, contact dnceng - search "Publish MSBuild 17.6 to NuGet.org" email subject for template).

  Following packages should be published (THIS_RELEASE_EXACT_VERSION is equal to VersionPrefix that comes form the eng\Version.props, that were part of the build we are trying to get published, it is as well part of the VS insertion PR noted above):

  • Microsoft.Build.Utilities.Core.{{THIS_RELEASE_EXACT_VERSION}}.nupkg
  • Microsoft.Build.{{THIS_RELEASE_EXACT_VERSION}}.nupkg
  • Microsoft.Build.Framework.{{THIS_RELEASE_EXACT_VERSION}}.nupkg
  • Microsoft.Build.Runtime.{{THIS_RELEASE_EXACT_VERSION}}.nupkg
  • Microsoft.Build.Tasks.Core.{{THIS_RELEASE_EXACT_VERSION}}.nupkg
  • Microsoft.NET.StringTools.{{THIS_RELEASE_EXACT_VERSION}}.nupkg
  • Microsoft.Build.Templates.{{THIS_RELEASE_EXACT_VERSION}}.nupkg

  Note: Microsoft.Build.Conversion.Core and Microsoft.Build.Engine are not part of the list. Microsoft.Build.Templates is part of the list. Those 3 packages are a difference to the historic publishing list.

• Publish docs: submit reference request at https://aka.ms/publishondocs

  • Click on the link labeled Request – Reference Publishing
  • You can use existing ticket as a reference

• Remove the temporarily added build feed from nuget.config if it was added in the Update the PackageValidationBaselineVersion step

• Update main subscriptions to the new channel (this can be done before or after release - depending on when the source repos from our previous - VS 18.3 - channle start to publish in the next - VS 18.4 - channel)
  darc get-subscriptions --exact --target-repo https://github.com/dotnet/msbuild --target-branch main

• Create the 18.3 release

  • Create tag (can be done upfront)

  git checkout <commit noted above>
  git tag v18.3.3
  git push upstream v18.3.3
  

  • Create Release in Github with Create Release from Tag GH option (https://github.com/dotnet/msbuild/releases/new?tag=v17.9.3) - the release notes can be prepopulated (Generate Release Notes)

• Extend the expiration date of the latest Opt-Prof data for vs18.3 branch.

  • Identify the location of the latest Opt-Prof data in VS Drop. The path should follow the format OptimizationData/DotNet-msbuild-Trusted/vs18.3/.... It can be found in the MSBuild CI logs of the "Build" task or alternatively, in the Opt-Prof pipeline logs under the "Publish OptimizationInputs drop" task.
  • Get drop.exe CLI tool.
  • Use this instruction to set the new expiration to (End of support date for the corresponding Visual Studio version) plus 3 months.

[MichalPavlik]

vs18.3 branch had wrong nuget version format and the pipeline is now broken due the optimization data issue. Use https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=13280050&view=results artifacts for the nuget push.

[MichalPavlik]

Doc publish: https://dev.azure.com/msft-skilling/Content/_workitems/edit/556447