From: Julian Seward <jseward@acm.org>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: This project needs a stable branch
Date: Tue, 20 Mar 2007 22:19:45 +0000 [thread overview]
Message-ID: <200703202219.46063.jseward@acm.org> (raw)
In-Reply-To: <200703151453.44831.paul@codesourcery.com>
On Thursday 15 March 2007 14:53, Paul Brook wrote:
> > Subsequent releases of the branch would contain no functionality
> > enhancements, but just bug fixes, with the eventual aim of achieving
> > 'it just works' status for any x86/x86_64 guest I try to install/run.
> > I know that's a tall order, and that 0.9.0 may not be able to supply
> > that for all guests. But it is an important goal to strive for.
>
> While I agree stability is a desirable goal, and there is obviously users
> want a stable product, I'm not sure a qemu is mature enough to make a
> stable branch worthwhile. Especially considering the very limited
> technical resources we have available.
Limited effort is always a problem, granted.
So here's a broader question, which I'm surprised nobody has asked
before (afaik). Think forward to a hypothetical QEMU 1.0 release.
What criteria are required for such a release?
J
next prev parent reply other threads:[~2007-03-20 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 11:11 [Qemu-devel] RFC: This project needs a stable branch Julian Seward
2007-03-15 13:48 ` Anthony Liguori
2007-03-15 14:11 ` Julian Seward
2007-03-15 14:53 ` Paul Brook
2007-03-15 15:34 ` Avi Kivity
2007-03-20 22:19 ` Julian Seward [this message]
2007-03-22 22:47 ` Rob Landley
2007-03-22 23:00 ` Johannes Schindelin
2007-03-22 23:23 ` Rob Landley
2007-03-22 23:27 ` Paul Brook
2007-03-22 23:57 ` Julian Seward
2007-03-23 0:35 ` Paul Brook
2007-03-23 0:37 ` Johannes Schindelin
2007-03-22 23:29 ` Thiemo Seufer
2007-03-22 23:45 ` Rob Landley
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=200703202219.46063.jseward@acm.org \
--to=jseward@acm.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).