Closed
Description
Tracking remaining work on msquic packaging
Windows:
- lack of automation to flow msquic to runtime (darc/maestro) (dotnet/runtime - 6.0)
- employ win preview images in runtime CI pipeline --> depends on https://github.com/dotnet/core-eng/issues/13582 (external)
Linux:
- automation to sign and publish to packages.microsoft.com (dotnet/msquic - 6.0)
- use msquic preloaded docker images in runtime CI pipeline
- use as many as possible docker images to run CI (7.0)
Miscellaneous:
- versioning needs to be more granular than 1.5.0 we have now, to actually push package updates 6.0 ❗ (dotnet/msquic - 6.0) - @wfurt
- 6.0 servicing - document "How to check if msquic version was bumped and if not, how to bump it" - @wfurt
- 7.0 - automation with bumps in numbers from dotnet/msquic
- missing package description
- separate crypto functions from baked in SSL and add dependency to the package - security 6.0 ❗ - @ManickaP --> Remove crypto functions from statically linked OpenSSL msquic#31
- branching and versioning post 6.0 branch = main becoming 7.0 6.0 ❗ - infra help needed, post 6.0 branching (dotnet/msquic - 6.0)
- for single file host we'll need to link msquic statically into runtime, see discussion in more fixes for msquic packaging #55607 (7.0)
- build packages with Debug MsQuic and use them in Debug builds and stress (7.0)