From: "Jeebs" <Jeebs@yango.us>
To: Qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu development schedule?
Date: Mon, 30 Aug 2004 16:44:34 -0500 [thread overview]
Message-ID: <000501c48eda$a026ab40$20649c3f@computername> (raw)
[I am *not* a developer, but since the user's list doesn't work, I lurk
here.]
What is the development schedule for Qemu?
In other words, what priority is there for various things?
Fabrice's recent comment about vastly speeding up Qemu got me thinking that
perhaps it might be better to work on other things first.
Don't misunderstand me... The recent discussion about performance
improvements, and Fabrice's comments were *very* exciting.
But I was just thinking that before you do the exciting and the 'sexy'
things, that perhaps you should work on the more mundane things needed to
make Qemu into a highly usable product.
Like vastly improving the user interface. Especially for Window's users
(such as myself.)
Improving the basic virtual system to add things like full Pentium-3
support. MMX, SSE, cpuid, etc. etc.
Making sure the FPU behaves like it's supposed to.
Improving data transfers to/from the guest / host.
And a bunch of other 'minor' details.
As I said above, I'm not a developer. So maybe I'm out of place even making
these questions and comments. If so, I apologize. I do indeed think Qemu
is an excellent project. It's very exciting and that's why I'm here
lurking.
I'm just a little concerned that maybe qemu might always be an incomplete,
un-stable, un-usable beta program. An interesting program without the
refinements and the polishing.
If all you ever do is work on the exciting stuff, and fix the occasional
problem, then the project may have trouble reaching the level of quality it
should.
That's why I was wondering what the project schedule actually was. At what
points are things going to be added or fixed or improved.
Or is Qemu still in the "free for all" early development stage where people
work on whatever exciting or sexy thing they feel like, with no actual plan
or organization?
next reply other threads:[~2004-08-30 21:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 21:44 Jeebs [this message]
2004-08-30 21:59 ` [Qemu-devel] Qemu development schedule? John R. Hogerhuis
2004-08-30 22:51 ` Jeebs
2004-08-31 11:59 ` Johannes Schindelin
2004-08-31 15:58 ` Jeebs
2004-08-31 16:27 ` Joe Batt
2004-08-31 17:42 ` Jeebs
2004-09-01 19:25 ` Kai Cherry
2004-09-01 19:33 ` andrej
2004-09-01 19:46 ` Joe Batt
2004-09-01 20:34 ` Mike Tremoulet
2004-09-01 20:46 ` Kai Cherry
2004-09-01 20:35 ` Kai Cherry
2004-09-02 20:46 ` Jim C. Brown
2004-09-03 7:52 ` [Qemu-devel] Filegetopt (Was: Qemu development schedule?) Renzo Davoli
2004-08-31 16:32 ` [Qemu-devel] Qemu development schedule? Johannes Schindelin
2004-08-31 17:40 ` Jeebs
2004-09-01 15:43 ` Lionel Ulmer
2004-09-01 17:03 ` John R. Hogerhuis
2004-09-01 19:07 ` Kai Cherry
2004-09-02 10:20 ` Info
2004-08-31 17:42 ` John R. Hogerhuis
2004-08-31 19:07 ` andrej
2004-08-31 19:44 ` Kai Cherry
2004-08-30 22:07 ` Hetz Ben Hamo
2004-08-30 22:59 ` Jeebs
2004-08-30 23:34 ` John R. Hogerhuis
2004-08-31 9:21 ` Kai Cherry
2004-08-31 10:15 ` Patrick Mauritz
2004-08-31 10:23 ` Kai Cherry
2004-08-31 17:23 ` Gianni Tedesco
2004-08-31 19:08 ` Kai Cherry
2004-09-01 20:53 ` Magnus Damm
2004-08-31 20:27 ` Fabrice Bellard
2004-08-31 21:50 ` René Korthaus
2004-09-01 22:04 ` Jim C. Brown
2004-08-31 22:02 ` Patrick Mauritz
2004-09-01 21:58 ` Jim C. Brown
2004-09-02 7:26 ` Lionel Ulmer
2004-09-02 20:56 ` Jim C. Brown
2004-09-02 23:28 ` Lionel Ulmer
2004-09-03 0:07 ` Jim C. Brown
2004-09-03 8:32 ` Fabrice Bellard
2004-09-03 7:29 ` Adrian Smarzewski
2004-09-03 8:28 ` Fabrice Bellard
2004-09-02 23:53 ` Daniel Serpell
2004-09-03 0:13 ` Jim C. Brown
2004-09-03 1:35 ` John R. Hogerhuis
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='000501c48eda$a026ab40$20649c3f@computername' \
--to=jeebs@yango.us \
--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).