Comment 8 for bug 2023531

#1a
> TL;DR: We keep the package as is in the archive and demote it to universe.
> We asked Microsoft to warn the User about EoL.
> You can also find more context about the discussion in the JIRA ticket FR-4855 [2]

Thanks for clarifying, that is at least a bit more comfortable to the users (compared to removing).
I like this new approach more.
But as I already hinted before, I think you really want/need also an SRU exception for this as well as it doesn't seem purely a MIR team decision.
Link the approved exception here please once done.
=> https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases

#1b - thanks, ok with it, thanks for spelling it out
=> Ack on this aspect

#1c - thanks, ok with it, thanks for documenting
=> Ack on this aspect

#3* llvm lld
Thanks for the clarification
=> Ack on this aspect

#4 only testing in autopkgtests

I'd prefer to have something not as gigantic in build time tests (read = "I agree to not add the huge thing, but something small maybe", just a reasonable sanity check).
But that isn't a hard requirement if there are good autopkgtests and there are.
You have lots of good "make the autopkgtest even better" and that might be where the time is indeed spend better now.
=> Ack on this aspect

#2 .git dir
Thanks for not giving up, I'm ok if this is solved in the mid-term
=> Ack on this aspect

#5 d/watch
Thanks for explaining, fixing and documenting.
I'm pleased to learn this will improve in the future
=> Ack on this aspect

The optional #6 / #7 will be covered by your longer list of known things you work on.
"""
1. Integrate (upstream) smoke tests into autopkgtest suite.
2. Investigate embedded third party dependencies that should/can be patched out of dotnet packages.
3. Patch out need for .git folder.
4. Investigate symbols tracking for .so and .dll files.
5. Investigate enabling LTO.
6a. Investigate state of JIT Tests.
6b. Investigate feasibility of integration into autopkgtest suite
"""

Thanks for stating this so clearly here.