Rich Lander

@mairaw -- I already added STS on this page: https://docs.microsoft.com/dotnet/core/introduction#support. Perhaps we can just do this as a rolling thunder type thing and merge this PR now?

I'll post a mirror copy of this at dotnet/announcements after a feedback period, possibly with changes. @terrajobst @mairaw @dcwhittaker @rbhanda

Hmmmm. I think that's right. We should change that guidance. @terrajobst?

You may be missing the point, Immo. The point is that the reference (like the one just above from dotnet/announcments) would be missing. That would be unfortunate. I consider that...

It's not that. It's not the back-ref from dotnet/announcements. I was just using that as an example. It's the back-ref from everywhere else that we cannot predit/expect.

Because we're making an announcement that by definition affects the ecosystem. If it doesn't, then it shouldn't be an announcement. Most discussions are much more narrow.

Nice! Yes, that looks about right. AssemblyLoadContext fits in in a .NET Core specific section. I'm sure we could get multiple people to help on this.

I like the scenario. I'm not sure how to solve it. We've had similar discussions, for secure-supply-chain scenarios. We wanted to determine if we could rebuild NuGet packages using sourcelink...

This looks great and has very high value. Turns out that modern scenarios require a lot of networking, right? Some things to consider (likely as advanced scenarios; unordered): - Sync...

We know that this change will break the website (mostly due to the same issue as https://github.com/dotnet/core/pull/7497). @mairaw would like to test this change, as you suggest, to see if...