mirror of https://github.com/xqemu/xqemu.git
Add some doc for the stable process.
-----BEGIN PGP SIGNATURE----- iQJGBAABCAAwFiEEw9DWbcNiT/aowBjO3s9rk8bwL68FAlqKoG8SHGNvaHVja0By ZWRoYXQuY29tAAoJEN7Pa5PG8C+vGWMQAIU0Xc4qLOA+YR4MLsEg+BWdUbRZbGoF zJXBOJ31MoZiFVKWPK8yhdqgtPCKVgmgQ/sZ5akZQkqOn29qM54nJRSP/E16mq4l ji1YE+esvaScDaI+52VTpfG5e23Im7Tb/HNByTR/FYj9lK2AEcRbDG+H5kA577fA fesHrwXZPnkhCq+6uHE/c/+ZAp1BMLqgteYqKH01jf/r5MJmUkRZhERpHvPPb2BC WNmsG0GAL1bRe7mkM3VZnyXzrVm/hhrKapCetRbYpMYclO5kHcX8zq1ECA/zWvet cOQw8phEn6kSnZsBxEZ4V7NNTLzLJD8VPNSMlAEtO1tZF2r1jF5FHAhImIFAnhyN khwRz5CKyt2B1Ze9cZe/iYExXaplAwz0N/C1MjQ9ylV/MR422rzE0pEfqFGmvje9 MJzB3rokXwVaOwEa46VupO6rcgr9PTWRAYNFK2kjkSoCjfh6dyvNNgHFlhjesNDC FhU/ZydpC5s0/e7UDx5/hrAxfewX6y7228ev/eYxd44ztyxXExW80CEXmuGpNNLs hMLMs9YHk+uxOI3Ielpm6dEq1LPXt4aB6Ae9ADrHM84q5BqkshJVg2EdZLcqpLgM +GxOkfRuVE97rLHjMRDJLvpVy/RjFgOaCElSQArotIm2sI8IYoqxZE4U+Rkoc9zm cT76eywq81uj =KSy0 -----END PGP SIGNATURE----- Merge remote-tracking branch 'remotes/cohuck/tags/stable-doc-20180219' into staging Add some doc for the stable process. # gpg: Signature made Mon 19 Feb 2018 10:01:19 GMT # gpg: using RSA key DECF6B93C6F02FAF # gpg: Good signature from "Cornelia Huck <conny@cornelia-huck.de>" # gpg: aka "Cornelia Huck <huckc@linux.vnet.ibm.com>" # gpg: aka "Cornelia Huck <cornelia.huck@de.ibm.com>" # gpg: aka "Cornelia Huck <cohuck@kernel.org>" # gpg: aka "Cornelia Huck <cohuck@redhat.com>" # Primary key fingerprint: C3D0 D66D C362 4FF6 A8C0 18CE DECF 6B93 C6F0 2FAF * remotes/cohuck/tags/stable-doc-20180219: docs: document our stable process Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
This commit is contained in:
Peter Maydell
commit
72f1094b6c
|
|
@ -0,0 +1,69 @@
|
|||
QEMU and the stable process
|
||||
===========================
|
||||
|
||||
QEMU stable releases
|
||||
--------------------
|
||||
|
||||
QEMU stable releases are based upon the last released QEMU version
|
||||
and marked by an additional version number, e.g. 2.10.1. Occasionally,
|
||||
a four-number version is released, if a single urgent fix needs to go
|
||||
on top.
|
||||
|
||||
Usually, stable releases are only provided for the last major QEMU
|
||||
release. For example, when QEMU 2.11.0 is released, 2.11.x or 2.11.x.y
|
||||
stable releases are produced only until QEMU 2.12.0 is released, at
|
||||
which point the stable process moves to producing 2.12.x/2.12.x.y releases.
|
||||
|
||||
What should go into a stable release?
|
||||
-------------------------------------
|
||||
|
||||
Generally, the following patches are considered stable material:
|
||||
- Patches that fix severe issues, like fixes for CVEs
|
||||
- Patches that fix regressions
|
||||
|
||||
If you think the patch would be important for users of the current release
|
||||
(or for a distribution picking fixes), it is usually a good candidate
|
||||
for stable.
|
||||
|
||||
|
||||
How to get a patch into QEMU stable
|
||||
-----------------------------------
|
||||
|
||||
There are various ways to get a patch into stable:
|
||||
|
||||
* Preferred: Make sure that the stable maintainers are on copy when you send
|
||||
the patch by adding
|
||||
|
||||
.. code::
|
||||
|
||||
Cc: qemu-stable@nongnu.org
|
||||
|
||||
to the patch description. By default, this will send a copy of the patch
|
||||
to ``qemu-stable@nongnu.org`` if you use git send-email, which is where
|
||||
patches that are stable candidates are tracked by the maintainers.
|
||||
|
||||
* You can also reply to a patch and put ``qemu-stable@nongnu.org`` on copy
|
||||
directly in your mail client if you think a previously submitted patch
|
||||
should be considered for a stable release.
|
||||
|
||||
* If a maintainer judges the patch appropriate for stable later on (or you
|
||||
notify them), they will add the same line to the patch, meaning that
|
||||
the stable maintainers will be on copy on the maintainer's pull request.
|
||||
|
||||
* If you judge an already merged patch suitable for stable, send a mail
|
||||
(preferably as a reply to the most recent patch submission) to
|
||||
``qemu-stable@nongnu.org`` along with ``qemu-devel@nongnu.org`` and
|
||||
appropriate other people (like the patch author or the relevant maintainer)
|
||||
on copy.
|
||||
|
||||
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, 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.
|
||||
Loading…
Reference in New Issue