Merge bitcoin-core#1576: doc: mention needs-changelog github label …

…in release process

759bd4b doc: mention `needs-changelog` github label in release process (Jonas Nick)

Pull request description:

ACKs for top commit:
  sipa:
    ACK 759bd4b

Tree-SHA512: fc38f0da81fee10c46dc22409d27dfe2742555991328554fc6b7eb3d1f3e50fea6213ebd10d5b58473aa89a21117a46f97b36f5cf50e7f95197a339ccc185447

doc/release-process.md

@@ -44,7 +44,8 @@ Perform these checks when reviewing the release PR (see below):
 1. Open a PR to the master branch with a commit (using message `"release: prepare for $MAJOR.$MINOR.$PATCH"`, for example) that
    * finalizes the release notes in [CHANGELOG.md](../CHANGELOG.md) by
        * adding a section for the release (make sure that the version number is a link to a diff between the previous and new version),
-       * removing the `[Unreleased]` section header, and
+       * removing the `[Unreleased]` section header,
+       * ensuring that the release notes are not missing entries (check the `needs-changelog` label on github), and
        * including an entry for `### ABI Compatibility` if it doesn't exist,
    * sets `_PKG_VERSION_IS_RELEASE` to `true` in `configure.ac`, and,
    * if this is not a patch release,