release process: mention targeted release schedule

This commit is contained in:
Jonas Nick 2023-05-12 14:19:52 +00:00
parent 165206789b
commit 79fa50b082
No known key found for this signature in database
GPG Key ID: 4861DBF262123605

View File

@ -12,6 +12,8 @@ It is best if the maintainers are present during the release, so they can help e
This process also assumes that there will be no minor releases for old major releases. This process also assumes that there will be no minor releases for old major releases.
We aim to cut a regular release every 3-4 months, approximately twice as frequent as major Bitcoin Core releases. Every second release should be published one month before the feature freeze of the next major Bitcoin Core release, allowing sufficient time to update the library in Core.
## Sanity Checks ## Sanity Checks
Perform these checks before creating a release: Perform these checks before creating a release: