Update VMR re-bootstrapping guidance #4284
Conversation
NikolaMilosavljevic
requested review from
MichaelSimons,
mthalman and
premun
as code owners
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
ghost
added
the
| 1. Update the arcade SDK version in the [global.json](https://github.com/dotnet/dotnet/blob/main/global.json). | ||
| 1. Update the arcade dependency commit and version in the [Version.Details.xml](https://github.com/dotnet/dotnet/blob/main/eng/Version.Details.xml). | ||
| 1. Update private source-built SDK and artifacts versions | ||
| 1. Update `PrivateSourceBuiltSdkVersion` and `PrivateSourceBuiltArtifactsVersion` in the [Versions.props](https://github.com/dotnet/dotnet/blob/main/eng/Versions.props). |
There was a problem hiding this comment.
All of these links of files that need to be updated should really be pointing to the installer repo since that's where the change needs to be made. This applies to other links in this doc as well.
There was a problem hiding this comment.
I've followed the existing model, that uses VMR links. @MichaelSimons ?
There was a problem hiding this comment.
That was a bad decision on my part.
There was a problem hiding this comment.
OK - fixing this now.
| 1. Find a [dotnet-source-build](https://dev.azure.com/dnceng/internal/_build?definitionId=1219) | ||
| with the desired changes. | ||
| 1. Retrieve the built SDKs from the following legs: | ||
| 1. Retrieve the built SDKs and PSB artifacts archives, from the following legs: |
There was a problem hiding this comment.
PSB should spelled out. To me PSB means previous SB artifacts but in this context you are really retrieving the current artifacts to use as the PSB when building the next release.
There was a problem hiding this comment.
Makes sense - will update to private source-built artifacts archive
3 participants
This PR adds: