Skip to content

Expand version checks to include more #31074

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

Open
1 of 2 tasks
dougbu opened this issue Mar 19, 2021 · 3 comments
Open
1 of 2 tasks

Expand version checks to include more #31074

dougbu opened this issue Mar 19, 2021 · 3 comments
Assignees
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework

Comments

@dougbu
Copy link
Member

dougbu commented Mar 19, 2021

  • Include everything we reference from assemblies in Microsoft.AspNetCore.App i.e. don't skip over System.IO.Pipelines or anything else from dotnet/runtime
    • This part is about updating our existing tests of Microsoft.AspNetCore.App.Ref and Microsoft.AspNetCore.App.Runtime.* content
  • Check the versions of the assemblies in all shipping packages
    • This part is more complicated because we need to baseline all expected versions from other repos, especially netstandard2.0 assemblies we reference from dotnet/runtime
    • Ignore patch versions of all .NET Framework assemblies and what they reference
    • Confirm w/ dotnet/runtime what assembly versions they plan to update while in 6.0 servicing
    • No need to open anything from other repos i.e. just check our assemblies and their references
@dougbu
Copy link
Member Author

dougbu commented Mar 19, 2021

/fyi @dotnet/aspnet-build I combined the testing bits into a single issue at least for now

@dougbu dougbu added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Mar 19, 2021
@wtgodbe wtgodbe added this to the Next sprint planning milestone Aug 12, 2021
@ghost
Copy link

ghost commented Aug 12, 2021

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@ghost
Copy link

ghost commented Sep 9, 2022

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

No branches or pull requests

4 participants
@adityamandaleeka @dougbu @wtgodbe and others