From: Avi Kivity <avi@redhat.com>
To: Farkas Levente <lfarkas@lfarkas.org>
Cc: KVM <kvm@vger.kernel.org>, Uri Lublin <ulublin@redhat.com>
Subject: Re: can we hope a stable version in the near future?
Date: Sun, 16 Nov 2008 18:14:43 +0200 [thread overview]
Message-ID: <492046F3.900@redhat.com> (raw)
In-Reply-To: <491811B4.6040700@lfarkas.org>
Farkas Levente wrote:
>> There is the maint/ series on git.kernel.org. It doesn't have formal
>> releases though.
>>
>
> do you plan any formal release? and it'd be nice to see the relationship
> between the current devel tree and the stable tree to eg. last stable
> 0.5 current devel 0.78.
>
The key to a formal release is a formal test suite. We've been building
one (for a long while) but it isn't in production yet.
The plan is for it to be open so people can add their favorite guests,
to ensure they will not regress.
> on the other hand the real question are you plan to somehow stabilize
> any of the following release in the near future? in the last 1.5 years
> we wait for this. or you currently not recommend and not plan to use kvm
> in production? it's also an option but would be useful to know. in this
> case we (and probably many others) switch to xen, virtualbox, vmware or
> anything else as a virtualization platform.
>
kvm is used in production on several products. Just not the kvm-nn
releases I make. The production versions of kvm are backed by testing,
which makes all the difference. Slapping a 'stable' label over a
release doesn't make it so.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-11-16 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 21:13 can we hope a stable version in the near future? Farkas Levente
2008-11-10 6:27 ` Brian Jackson
2008-11-10 10:29 ` Avi Kivity
2008-11-10 10:49 ` Farkas Levente
2008-11-16 16:14 ` Avi Kivity [this message]
2008-11-18 22:07 ` Farkas Levente
2008-11-19 9:40 ` Dor Laor
2008-11-19 9:59 ` Farkas Levente
2008-11-19 15:23 ` Dor Laor
2008-11-10 11:01 ` Martin Maurer
2008-11-10 11:31 ` Farkas Levente
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=492046F3.900@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lfarkas@lfarkas.org \
--cc=ulublin@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox