public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Farkas Levente <lfarkas@lfarkas.org>
Cc: KVM <kvm@vger.kernel.org>
Subject: Re: can we hope a stable version in the near future?
Date: Mon, 10 Nov 2008 12:29:49 +0200	[thread overview]
Message-ID: <49180D1D.9000409@redhat.com> (raw)
In-Reply-To: <4917525D.709@lfarkas.org>

Farkas Levente wrote:
> hi,
> i've to repeat myself old mail again:
> http://article.gmane.org/gmane.comp.emulators.kvm.devel/18095
>
> i see there is a lots of development in kvm lately. there are many
> people working on many thing, but most of them improvements and
> extensions. and those who read the list can see there are many basic
> problems too. rhel/centos-5 host can't boot mandrake-10 guest, fedora
> latest kernel guest, rhel/centos-5 x86-64 guest crash during boot,
> 100%cpu usage, rhes-4 can't boot etc.
> so imho it'd be useful to release a kvm version which fix all known bug
> and may be start a new branch for development asap.
> how long do you plan to keep kvm in a development stage without a stable
> release?
> i know it'll be a bit complicated to maintain 4 different tree (devel,
> stable x kernel, userspace), but it'd be very useful from the user's
> point of view.
>   

There is the maint/ series on git.kernel.org.  It doesn't have formal 
releases though.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2008-11-10 10:29 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 [this message]
2008-11-10 10:49   ` Farkas Levente
2008-11-16 16:14     ` Avi Kivity
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=49180D1D.9000409@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lfarkas@lfarkas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox