diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2019-06-08 17:35:22 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2019-06-08 17:36:02 +0200 |
| commit | 8a503a6c6dd419921373f45d7aa6f1787c9b8884 (patch) | |
| tree | a7e21913ae7486d485ee6ee4946a172a33d532ab /src | |
| parent | 70d77fff3a8d54d2f0e347f7d93d7b11eb18597d (diff) | |
| parent | d7c054277798cc1975041eb19c679cd07c412d68 (diff) | |
Merge #16164: doc: update release process for SECURITY.md
d7c054277798cc1975041eb19c679cd07c412d68 doc: update release process with SECURITY.md (Jon Atack)
e4e2b28cf1c87699e5c86e75e066636ba2a9c146 doc: clarify support in SECURITY.md (Jon Atack)
Pull request description:
Follow-up to https://github.com/bitcoin/bitcoin/pull/16140:
- Update the release process to maintain SECURITY.md; this looks like the sort of item that can otherwise be easily overlooked during a major release
- Clarify type of support in SECURITY.md
Question: If https://bitcoincore.org/en/lifecycle/#maintenance-period is still current policy, should v0.15 now be unmaintained and v0.16 EOL... seems the schedule on that page could use an update.
ACKs for commit d7c054:
practicalswift:
ACK d7c054277798cc1975041eb19c679cd07c412d68
fanquake:
ACK https://github.com/bitcoin/bitcoin/pull/16164/commits/d7c054277798cc1975041eb19c679cd07c412d68. This seems to make sense.
Tree-SHA512: ce0f832d9804d7bfd29f2361948d7d6a4e93004a1f57e07a95dfba056caa4d8c4552267c66e6728b689b0309f4688c2d8d59d7b0c26b838c6a30df878a69fceb
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions