From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: This project needs a stable branch
Date: Thu, 15 Mar 2007 14:11:53 +0000 [thread overview]
Message-ID: <200703151411.53494.jseward@acm.org> (raw)
In-Reply-To: <45F94E97.10502@codemonkey.ws>
On Thursday 15 March 2007 13:48, Anthony Liguori wrote:
> I'm not necessarily sure I agree that a stable branch is the best thing
> to have (verses aiming for never introducing regressions).
Aiming for no regressions is a worthy aim, but I believe unachieveable
in a project of any size. For sure it's impossible if there is ever a
need to make large-scale infrastructural changes, which inevitably is
occasionally the case if the project is to live a long time.
For example, if the dyngen/gcc-based backend is replaced by a
self-contained handwritten one, I would be amazed if there were not
a few obscure regressions whilst the new backend is brought up to the
same level of stability as the current one. At least, that is what
I know from my own code generator hacking.
J
next prev parent reply other threads:[~2007-03-15 14:15 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 [this message]
2007-03-15 14:53 ` Paul Brook
2007-03-15 15:34 ` Avi Kivity
2007-03-20 22:19 ` Julian Seward
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=200703151411.53494.jseward@acm.org \
--to=jseward@acm.org \
--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 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.