From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: RE: Bug tracking system
Date: Wed, 13 Apr 2005 16:08:31 -0500 [thread overview]
Message-ID: <1113426511.13307.1.camel@localhost> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3B40@liverpoolst.ad.cl.cam.ac.uk>
On Wed, 2005-04-13 at 15:49, Ian Pratt wrote:
> We discussed this a bit at the summit. We have 'trac' set up and ready
> to go, but we weren't planning on announcing it until we fork off
> 3.0-testing around the end of May/ beginning of June. If there was
> strong demand, we'd obviously revist this, but my impression is that the
> mailing lists are working effectively and bugs generally get fixed
> pretty quickly. (Last week and this have been a bit tough because of the
> summit and now Usenix TC)
I personally think we need something for the interim. I'm not sure
whether we need a full bug database but we at least need something to
keep a list of current issues. (Perhaps a page on the wiki?)
Regards,
> The other issue that was raised was whether we need to go with bugzilla
> to be able to integrate in to distro bug databases. We certainly prefer
> trac, but if we need the ability to assign bugs between databases, I
> guess we'll have to go with bugzilla.
> Any views?
>
> Thanks,
> Ian
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
--
Anthony Liguori
Linux Technology Center (LTC) - IBM Austin
E-mail: aliguori@us.ibm.com
Phone: (512) 838-1208
next prev parent reply other threads:[~2005-04-13 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 20:49 Bug tracking system Ian Pratt
2005-04-13 21:06 ` Nivedita Singhvi
2005-04-13 21:08 ` Anthony Liguori [this message]
2005-04-13 21:17 ` Paul Larson
2005-04-13 23:02 ` Ryan Harper
-- strict thread matches above, loose matches on Subject: below --
2014-08-14 14:55 Ralf Baechle
2014-08-14 15:09 ` James Hogan
2014-08-14 15:09 ` James Hogan
2014-08-14 15:22 ` Ralf Baechle
2005-04-13 17:35 Paul Larson
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=1113426511.13307.1.camel@localhost \
--to=aliguori@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.