Expand version checks to include more

dotnet / aspnetcore

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.

https://asp.net

MIT License

35.59k stars 10.06k forks source link

Expand version checks to include more #31074

Open dougbu opened 3 years ago

dougbu commented 3 years ago

[x] 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 commented 3 years ago

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

ghost commented 3 years ago

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 commented 2 years ago

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.