From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Request for Qemu bugzilla
Date: Mon, 7 Jan 2008 21:38:54 +0100 [thread overview]
Message-ID: <200801072138.54505.jseward@acm.org> (raw)
In-Reply-To: <7F1725D0-A829-49F5-887A-AEECEAE01FE3@web.de>
> [discussion about where to host a bugzilla]
Perhaps a more important question is, is there interest in making
a stable branch, tracking bugs and producing bug-fix-only releases
from the stable branch? As is traditional in (eg) gcc, etc? If not,
I don't think there is much point in having a bugzilla.
> While QEMU is officially still in alpha stage ;) I'd agree that an
> issue tracking system can be useful.
It could be argued that QEMU would be more likely to move beyond
alpha state if these traditional kinds of QA mechanisms were actually
put into place and then used.
J
next prev parent reply other threads:[~2008-01-07 20:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 18:56 [Qemu-devel] Request for Qemu bugzilla Alexey Eremenko
2008-01-06 19:06 ` Andreas Färber
2008-01-06 19:12 ` Soren Hansen
2008-01-06 19:56 ` Daniel P. Berrange
2008-01-06 20:35 ` Soren Hansen
2008-01-06 21:13 ` Alexey Eremenko
2008-01-07 20:38 ` Julian Seward [this message]
2008-01-07 22:09 ` Andreas Färber
2008-01-08 1:18 ` Rob Landley
2008-01-08 17:51 ` Lauro Ramos Venancio
2008-01-08 18:23 ` Alexey Eremenko
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=200801072138.54505.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.