The repo should not contain documentation that is not tied to any release. For example meta information like a list of maintained versions of Bitcoin Core falls into this scope.
Replace the list of versions in ./SECURITY.md with a link to the website.
Just to understand the context: what changed since #16140 (comment)? :-)
I think we should also move the EOL policy from the website into the repo, but that might be also good for a follow up pull request.
With "good for a follow up pull request" I meant that it might be controversial. My primary point was that the policy should only be maintained in one place.
@practicalswift This was discussed on the IRC meeting yesterday.
ACK https://github.com/bitcoin/bitcoin/pull/16213/commits/fa4bc4ebf91e2bf4732063f7a374a98902436a7c
IRC discussion is available here (starting line 626).
ACK fa4bc4ebf91e2bf4732063f7a374a98902436a7c
ACK fa4bc4ebf91e2bf4732063f7a374a98902436a7c
