From: Asdo <asdo@shiftmail.org>
To: "'KVM-ML (kvm@vger.kernel.org)'" <kvm@vger.kernel.org>
Subject: Regarding "stable" kvm releases
Date: Thu, 03 Feb 2011 15:59:52 +0100 [thread overview]
Message-ID: <4D4AC2E8.9050602@shiftmail.org> (raw)
Hello list
I know qemu-kvm versions from sourceforge are the "stable" kvm releases.
So I went there hoping to find a version maintainance policy like that
of the linux kernel, that is, the last number in the release version is
the patch level.
Usually in linux I go hunting for the last kernel version which ends
with a .3 or higher, for production use, e.g. as of today I wouldn't
choose 2.6.37(.0) beacause .0 is not enough stable for a production
server imho, I would choose 2.6.36.3
I was trying to do the same with KVM but when I saw the changelogs I
realized that the stable kvm releases are not really stable in this sense.
E.g. in the 0.12.4 there are a helluva lot of changes which are feature
improvements (hence adding potential bugs), or so seems to me:
http://garr.dl.sourceforge.net/project/kvm/qemu-kvm/0.12.4/changelog
Am I correct? So there is no "maintenance line" in KVM where, after a
release with new features, you only add bugfixes for later point-versions?
So our likelihood of getting regression bugs is basically the same for
every qemu-kvm version; so we should just choose the latest qemu-kvm,
i.e. right now we should choose 0.13.0 instead of 0.12.5 ?
Thank you
reply other threads:[~2011-02-03 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D4AC2E8.9050602@shiftmail.org \
--to=asdo@shiftmail.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.