aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2019-06-08 17:35:22 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2019-06-08 17:36:02 +0200
commit8a503a6c6dd419921373f45d7aa6f1787c9b8884 (patch)
treea7e21913ae7486d485ee6ee4946a172a33d532ab
parent70d77fff3a8d54d2f0e347f7d93d7b11eb18597d (diff)
parentd7c054277798cc1975041eb19c679cd07c412d68 (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
-rw-r--r--SECURITY.md2
-rw-r--r--doc/release-process.md2
2 files changed, 4 insertions, 0 deletions
diff --git a/SECURITY.md b/SECURITY.md
index 80b41030b7..4044722374 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -2,6 +2,8 @@
## Supported Versions
+Versions of Bitcoin Core that are currently supported with security updates:
+
| Version | Supported |
| ------- | ------------------ |
| 0.18 | :white_check_mark: |
diff --git a/doc/release-process.md b/doc/release-process.md
index 2e712bf58e..8f1222cb88 100644
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -41,10 +41,12 @@ Release Process
#### After branch-off (on master)
- Update the version of `contrib/gitian-descriptors/*.yml`.
+- Update the versions in `SECURITY.md` as per the software lifecycle [maintenance policy](https://bitcoincore.org/en/lifecycle/#maintenance-period), generally bumping all up one major version.
#### After branch-off (on the major release branch)
- Update the versions and the link to the release notes draft in `doc/release-notes.md`.
+- Delete `SECURITY.md`.
#### Before final release