 Home |
Products |
Support |
Community |
News |
xen-devel
Re: Fw: [Xen-devel] Bug tracking system
| To: | xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Fw: [Xen-devel] Bug tracking system |
| From: | Kip Macy <kip.macy@xxxxxxxxx> |
| Date: | Wed, 13 Apr 2005 10:47:09 -0700 |
| Delivery-date: | Wed, 13 Apr 2005 17:47:03 +0000 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RdmG3ozFjVNAtPMWYSE7bS6V1kqBQg3vLtl/gscp56pUQzk/8V6VXyuUs7ftgossrQIFbhjRtzfxTMczJnfMu+021gfHsP6JEw6AF95af2r8DQfvT2U7OWbxDWgvPrCErX/JKUQocBGW7/O9xuWWjK5TQRG6knWfwOXRLmpIRRY= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <OF0D0F8113.52FD2D19-ON86256FE2.0060CBC7-86256FE2.00611266@xxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <OF0D0F8113.52FD2D19-ON86256FE2.0060CBC7-86256FE2.00611266@xxxxxxxxxx> |
| Reply-to: | Kip Macy <kip.macy@xxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
There was some talk of using TRAC. The only argument given for not
having one yet is waiting until -unstable is stable enough that the
reported bugs are actual bugs and not artifacts of incompletely
implemented features.
I understand the reasoning, but it would be nice to have a better
mechanism for determining if a problem one is seeing is new or not.
-Kip
On 4/13/05, Stephanie Glass <sglass@xxxxxxxxxx> wrote:
>
>
> >Paul Larson wrote:
> >
> >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.
>
> Stephanie Glass
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] Re: softirq change was Re: domu_debug support removed on march 25th from traps.c in -unstable, Keir Fraser |
|---|---|
| Next by Date: | [Xen-devel] Re: softirq change was Re: domu_debug support removed on march 25th from traps.c in -unstable, Kip Macy |
| Previous by Thread: | Fw: [Xen-devel] Bug tracking system, Stephanie Glass |
| Next by Thread: | RE: [Xen-devel] Bug tracking system, Ian Pratt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
