-
Notifications
You must be signed in to change notification settings - Fork 438
Update 6.0.2xx with the current state of 1xx #13244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
marcpopMSFT
commented
Feb 17, 2022
- Please add description for changes you are making.
- If there is an issue related to this PR, please add the reference.
…ence-packages build 20220205.1 (#13179) [release/6.0.1xx] Update dependencies from dotnet/source-build-reference-packages
…ild in Roslyn (#13093) * override SDK for Microsoft.Net.Sdk.WindowsDesktop references in roslyn * add new EmptySdk in the source build tarball * remove roslyn solution filter patch
…207.2 (#13186) Microsoft.DotNet.CMake.Sdk , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Arcade.Sdk From Version 6.0.0-beta.22102.3 -> To Version 6.0.0-beta.22107.2 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…-merge-6.0.1xx-2022-02-08-1019
[release/6.0.1xx] Windows SDK projection update
…-2022-02-08-1019 Merging internal commits for release/6.0.1xx
…ence-packages build 20220210.1 (#13215) [release/6.0.1xx] Update dependencies from dotnet/source-build-reference-packages
…ence-packages build 20220215.1 (#13229) [release/6.0.1xx] Update dependencies from dotnet/source-build-reference-packages
|
@MichaelSimons , should I continue to expect significant changes for source build in the 1xx branch? For 5.0 servicing we didn't auto-merge other than N-1 to main but it seems like with 6.0, there have been a lot of 1xx changes (and potentially .2xx changes) which are requiring manual merging. |
Yes, source-build has traditionally only supported the oldest sdk channel per agreement with our SB partners. We would like to get to the point where we support all channels but don't have the resources to support that at the moment. The primary changes being made in 1xx is all related to testing and eng infra to automate the release process. I expect this will slow down drastically in a couple more servicing releases but there will still be occasional changes needed. |
|
@MichaelSimons if ya'll are going to focus on the oldest but the SDK teams are focused on the newest, do you think you'd be able to pick up owning the manual merge forward or should we enable auto-merge forward? |
|
Please enable auto-merge forward. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@MichaelSimons Any suggestions on this tarbal failure: |
|
@marcpopMSFT - I opened dotnet/source-build#2783 to track the underlying issue. Feel free to merge. The fix will flow in from dotnet/source-build-reference-packages |
|
Thinking about this more, I will fix the issue right away and update this PR. |
…ence-packages build 20220303.2 Microsoft.SourceBuild.Intermediate.source-build-reference-packages From Version 6.0.0-servicing.22151.1 -> To Version 6.0.0-servicing.22153.2
|
I cherry-picked the fix for the tarball failure. |