diff options
| author | Alex Bennée | 2022-11-17 18:25:23 +0100 |
|---|---|---|
| committer | Alex Bennée | 2022-11-22 10:49:07 +0100 |
| commit | 668725ce6bab12f7d5130fd46d99d0dc6fefe733 (patch) | |
| tree | 19c6686da5a2eb3a73f912f3e24ee0d8f55ce35a /docs/devel/submitting-a-pull-request.rst | |
| parent | tests/docker: allow user to override check target (diff) | |
| download | qemu-668725ce6bab12f7d5130fd46d99d0dc6fefe733.tar.gz qemu-668725ce6bab12f7d5130fd46d99d0dc6fefe733.tar.xz qemu-668725ce6bab12f7d5130fd46d99d0dc6fefe733.zip | |
docs/devel: add a maintainers section to development process
We don't currently have a clear place in the documentation to describe
the roles and responsibilities of a maintainer. Lets create one so we
can. I've moved a few small bits out of other files to try and keep
everything in one place.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-Id: <20221117172532.538149-5-alex.bennee@linaro.org>
Diffstat (limited to 'docs/devel/submitting-a-pull-request.rst')
| -rw-r--r-- | docs/devel/submitting-a-pull-request.rst | 12 |
1 files changed, 4 insertions, 8 deletions
diff --git a/docs/devel/submitting-a-pull-request.rst b/docs/devel/submitting-a-pull-request.rst index c9d1e8afd9..a4cd7ebbb6 100644 --- a/docs/devel/submitting-a-pull-request.rst +++ b/docs/devel/submitting-a-pull-request.rst @@ -53,14 +53,10 @@ series) and that "make check" passes before sending out the pull request. As a submaintainer you're one of QEMU's lines of defense against bad code, so double check the details. -**All pull requests must be signed**. If your key is not already signed -by members of the QEMU community, you should make arrangements to attend -a `KeySigningParty <https://wiki.qemu.org/KeySigningParty>`__ (for -example at KVM Forum) or make alternative arrangements to have your key -signed by an attendee. Key signing requires meeting another community -member \*in person\* so please make appropriate arrangements. By -"signed" here we mean that the pullreq email should quote a tag which is -a GPG-signed tag (as created with 'gpg tag -s ...'). +**All pull requests must be signed**. By "signed" here we mean that +the pullreq email should quote a tag which is a GPG-signed tag (as +created with 'gpg tag -s ...'). See :ref:`maintainer_keys` for +details. **Pull requests not for master should say "not for master" and have "PULL SUBSYSTEM whatever" in the subject tag**. If your pull request is |