Update branch-checklist.md to include instructions on updating the VS installer channel to be used in the "Build VS Bootstrapper" task. This bootstrapper is used to install VS for capturing optimization data, and combines a baseline VS build (from the specified channel) with the Project System components produced by the build. The versions of these two inputs need to match--e.g., if we're building the dev17.8.x branch of dotnet/project-system, the baseline VS build needs to come from the 17.8 channel. Combining mismatched versions may prevent the project system from loading during the test and producing useful optimization data.
This also removes the step to setup automatic PRs from release branches back to main. These automatic PRs are rarely useful; once we've created a release branch we're generally late in the release cycle and expect to take few, if any, changes to the release branch. And for servicing fixes after release we have to test them first in main anyway, and so the automatic PR won't do anything useful. On the other hand we definitely don't want any changes to the bootstrapper channel to go back into our main branch.
Update branch-checklist.md to include instructions on updating the VS installer channel to be used in the "Build VS Bootstrapper" task. This bootstrapper is used to install VS for capturing optimization data, and combines a baseline VS build (from the specified channel) with the Project System components produced by the build. The versions of these two inputs need to match--e.g., if we're building the
dev17.8.xbranch of dotnet/project-system, the baseline VS build needs to come from the 17.8 channel. Combining mismatched versions may prevent the project system from loading during the test and producing useful optimization data.This also removes the step to setup automatic PRs from release branches back to
main. These automatic PRs are rarely useful; once we've created a release branch we're generally late in the release cycle and expect to take few, if any, changes to the release branch. And for servicing fixes after release we have to test them first inmainanyway, and so the automatic PR won't do anything useful. On the other hand we definitely don't want any changes to the bootstrapper channel to go back into ourmainbranch.Microsoft Reviewers: Open in CodeFlow