docs: clarify wording in README.md

This commit is contained in:
Pavitthra Pandurangan
2022-01-13 10:30:04 -05:00
parent 0e5de8f4e1
commit 51ec5a0b26

View File

@@ -395,8 +395,8 @@ discussed in [Versioning](#versioning). We assume, in this section,
that the change is not consensus-breaking. So, the release manager must first
determine whether there are any "non-consensus-breaking changes that require a
fresh chainstate". This means, in other words, that the database schema has
changed. Then, the release manager should determine whether this is a feature
release, as opposed to a hot fix or a patch. Given the answers to these
changed without a migration. Then, the release manager should determine whether this
is a feature release, as opposed to a hot fix or a patch. Given the answers to these
questions, the version number can be computed.
1. The release manager enumerates the PRs or issues that would _block_