Re: [Qemu-devel] [PATCH v2] docs: document our stable process

[Eric Blake <eblake@redhat.com>]

On 02/12/2018 06:40 AM, Cornelia Huck wrote:
> Some pointers on how to get a patch into stable.
> 
> [contains some suggestions by mdroth]
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> RFC/D->v2: added mdroth's suggestions
> ---
>   docs/stable-process.rst | 67 +++++++++++++++++++++++++++++++++++++++++++++++++
>   1 file changed, 67 insertions(+)
>   create mode 100644 docs/stable-process.rst
> 

> +     Cc: qemu-stable@nongnu.org
> +
> +  to the patch description. By default, this will send a copy of the  patch

Spurious double space.

> +  to ``qemu-stable@nongnu.org`` if you use git send-email, which is where
> +  patches that are stable candidates are tracked by the maintainers.
> +

> +Stable release process
> +----------------------
> +
> +When the stable maintainers prepare a new stable release, they will prepare
> +a git branch with a release candidate and send the patches out to
> +``qemu-devel@nongnu.org`` for review. If any of your patches are included,
> +please verify that they look fine.

Maybe add: especially if the maintainer had to tweak the patch as part 
of back-porting things across branches.


>        You may also nominate other patches that
> +you think are suitable for inclusion. After review is complete (may involve
> +more release candidates), a new stable release is made available.
> 

What you have is an obvious improvement over the "nothing" that was 
before, so whether or not you fold in my additional comments, you can add:

Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org