Double-tagging in VMR repo for each release

[mthalman]

For the past two releases of .NET 10 (Preview 7, RC 1), there have been two tags created in the VMR for each of those releases. These correspond to the runtime and SDK versions.

• https://github.com/dotnet/dotnet/tree/v10.0.0-preview.7.25380.108
• https://github.com/dotnet/dotnet/tree/v10.0.100-preview.7.25380.108
• https://github.com/dotnet/dotnet/tree/v10.0.0-rc.1.25451.107
• https://github.com/dotnet/dotnet/tree/v10.0.100-rc.1.25451.107

[MichaelSimons]

[Triage] Ella, please work with the prod con team to explain the background and potential issues with multiple feature bands.

[ellahathaway]

I discussed this with offline with @pavel-purma. He said that while they have not been able to test multi-band releases from the VMR, he said that he expects that the runtime tag will always be on the 1xx feature band.

We also spoke about where the tagging occurs in the release infra. I was told that there is a single place where the tagging occurs during the release process and that SDK release tags are not currently being created. This means that there should not be any incompatibility with the SB release infra. Also see https://github.com/dotnet/release/issues/1561.

Given these things, I don't see any further action that needs to be taken to resolve this issue.

[mthalman]

he said that he expects that the runtime tag will always be on the 1xx feature band.

But why? The intention of the VMR is to produce an SDK. And when you look at the sdk repo, it's not using runtime version tagging; it's using the SDK version for the tags. This is how the VMR should operate as well.

[ellahathaway]

But why? The intention of the VMR is to produce an SDK. And when you look at the sdk repo, it's not using runtime version tagging; it's using the SDK version for the tags. This is how the VMR should operate as well.

I was told that the prod con team came to the tagging conclusion with @mmitche and that it has something to do with the tag for runtime and SDK being on different repos when we were releasing from MS build.

Maybe Matt and Pavel can provide more insight?

[mmitche]

I know we discussed this in depth at some point. I hunted around but was unable to find the discussion or decisions. I think I lean towards double tagging:

• The SDK tag points to source that can produce the 1xx or 2xx or 3xx SDK.
• The runtime tag points to source that can produce the runtime. Even if the 1xx SDK is also produced in the process, this is useful information IMO.
• The 2xx/3xx SDK tags cannot produce a runtime. The sources for the runtime aren't even in the VMR there. I think the double tag makes this a bit clearer.