All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Stephanie Glass <sglass@us.ibm.com>
Subject: Re: Bug tracking system
Date: Wed, 13 Apr 2005 18:02:35 -0500	[thread overview]
Message-ID: <20050413230235.GC27571@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3B40@liverpoolst.ad.cl.cam.ac.uk>

* Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> [2005-04-13 15:50]:
> > >There was some discussion some time ago about a bug tracking 
> > system for 
> > >Xen.  Is there any plan on when that will be available?
> > 
> > I like to vote for the bug tracking system to come sooner 
> > versus later.  I have notice that there are several bugs that 
> > keep coming back up on the mailing list and if we had a bug 
> > track tracking system, we would be able to put it out once.  
> > Then as people have time, they could pick different bugs and 
> > supply fixes for them by assinging the bug to themselves.
> 
> 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)
> 
> 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?

The sooner a bug database is up, whether trac or bugzilla the better.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

  parent reply	other threads:[~2005-04-13 23:02 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
2005-04-13 21:17   ` Paul Larson
2005-04-13 23:02 ` Ryan Harper [this message]
  -- 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=20050413230235.GC27571@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=sglass@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.