dotnet-bot commented 2 years ago

Migrated from https://github.com/dotnet/core-eng/issues/13814

@markwilkie wrote:

From SDK team:

Check if any releases need insertion (10 workdays before ship date) or push for a insert ready build (13 - 10 workdays before ship date). Reference Shipping dates session.
If there are build within "push for a insert ready build" period, but not ready. Investigate the reason and notify the team. Reference "push for a insert ready build".
If insertion is needed. Make the insertion (5.0 branches does not need insertion) reference Insertion

https://microsoft-:my.sharepoint.com/:x:/p/wul/ERRzj81D6eZEjUHQAL7UoLMBXFXcTBHD2dHMio4IPodpaw?e=yF9r0q

Recently Triaged Issues

All issues in this section should be triaged by the v-team into one of their business objectives or features.

markwilkie commented 2 years ago

@marcpopMSFT - Given that I think you've got a vendor on this, should we continue to keep this on our radar?

marcpopMSFT commented 2 years ago

In theory, I think this was for auto-detecting a coherent build and triggering an insertion. I agree that our vendor mostly takes care of this. Is there some benefit to auto-coherency detection?

markwilkie commented 2 years ago

This is needed more when we're inserting weekly VS builds.

mmitche commented 2 years ago

@marcpopMSFT I think we should close this. I don't think we really ever have a coherent build unless we try and make one explicitly.

dotnet / arcade-services

Ensure build is ready to insert into VS #2363

Recently Triaged Issues