All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: James Bulpin <james@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen bugzilla
Date: Fri, 22 Apr 2005 09:06:37 -0700	[thread overview]
Message-ID: <4269210D.2000501@us.ibm.com> (raw)
In-Reply-To: <1114184000.23365.177.camel@plym.cl.cam.ac.uk>

James Bulpin wrote:
> Folks,
> 
> As requested we now have a bugzilla bug tracker for the Xen project. It
> is available at http://bugzilla.xensource.com/ 
> 
> Registration is required to submit and modify bug reports. We hope to
> support anonymous reports in the near future. 
> 
> Please let me know of any problems or suggestions, extra components,
> categories, etc. desired.

Excellent job, guys, much thanks! I logged in and could create an
account in under a 30 seconds, email exchange and all.

Just a few trivial questions:

1. The Component field has the following:
    Guest-OS, Hardware support, hypervisor, tools and unspecified.

    Would dom0 issues be spread out across the non-GuestOS
    category?

    Commonest problems reported:
	- build/compile/boot
	- configuration of networking/storage devices
	
     Where would those go?

2. The Version field has 2.0, unstable, unspecified.
    Do you want -testing as a separate category or in the 2.0
    bucket? Are you going to add the individual releases
    2.0.4, 2.0.5, etc? The finer granularity in the Version
    field does make it easier to search - especially once
    you have a long history :).

thanks,
Nivedita

  reply	other threads:[~2005-04-22 16:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22 15:33 Xen bugzilla James Bulpin
2005-04-22 16:06 ` Nivedita Singhvi [this message]
2005-04-22 16:34   ` James Bulpin
2005-04-22 17:16   ` Paul Larson
2005-04-22 20:25 ` Paul Larson
2005-04-23 13:34   ` James Bulpin

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=4269210D.2000501@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=james@xensource.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.