mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-22 13:45:38 +00:00
docs: patches: Add a note about reviews and contacting developers
Add a note outling best practices around review and responding to it. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
This commit is contained in:
parent
06a9dcb35d
commit
80e50315b4
@ -89,3 +89,24 @@ Moreover, such patch needs to be prefixed correctly with
|
||||
``--subject-prefix=PATCHv2`` appended to
|
||||
``git send-email`` (substitute ``v2`` with the
|
||||
correct version if needed though).
|
||||
|
||||
Review process
|
||||
--------------
|
||||
|
||||
Reviewing patches may take a lot of effort with review bandwidth being limited
|
||||
in open source projects. Here are a few rules to follow to streamline the
|
||||
process:
|
||||
|
||||
- **don't** contact individual maintainers/developers directly with your
|
||||
patches; reviewers are subscribed to the mailing list
|
||||
- **do** be patient; reviewers may be busy
|
||||
- **do** respond to reviewer's questions
|
||||
- **don't** ignore a suggestion from a reviewer; if you disagree discuss it on
|
||||
the list before sending a new version
|
||||
- **do** remind us of your patches on the list if they haven't gotten any
|
||||
attention for a prolonged period (>1 week) by replying to your patches with a
|
||||
"ping"
|
||||
- **do** test your patches before sending
|
||||
|
||||
Don't feel obliged to review whole patch series if you see any major problems
|
||||
in any of the comprising patches - just point them out on the list.
|
||||
|
Loading…
Reference in New Issue
Block a user