Xen bugzilla

Xen bugzilla

[James Bulpin]

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.

Cheers,

James

Re: Xen bugzilla

[Nivedita Singhvi]

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

Re: Xen bugzilla

[James Bulpin]

On Fri, 2005-04-22 at 17:06, Nivedita Singhvi wrote:
> 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?

Hmm, perhaps "Guest-OS" isn't the best name - we wanted that component
to be for operating systems running on Xen, i.e. dom0 and domU. Ideally
we'd have a different field for domU/dom0/both but that doesn't fit in
the bugzilla schema :-(.

My suggestion would be that bugs that are clearly related to a domain
running on Xen, which may only manifest themselves in dom0 get assigned
to "Guest-OS" while bugs that are clearly hardware/driver go in
"hardware support". Anything else can be assigned "unspecified"  - it's
easy to reassign bugs once submitted. Once we see more bugs being
reported we'll get a better idea of how to organise that field.

>     Commonest problems reported:
> 	- build/compile/boot

If the compile bug or boot crash was in Xen then under "hypervisor", in
Linux/BSD under "Guest-OS" etc. Anything else can go in unspecified.

> 	- configuration of networking/storage devices

Not sure things on this topic would be bugs. We can keep higher-level
stuff like this on the lists.

> 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 :).

We were intending 2.0 to cover the -testing and releases (a 2.0.x is
just a snapshot of 2.0-testing anyway). I guess there is no harm in
having specific releases here as well.

James

Re: Xen bugzilla

[Paul Larson]

[-- Attachment #1.1: Type: text/plain, Size: 1521 bytes --]

On Fri, 2005-04-22 at 09:06 -0700, Nivedita Singhvi wrote:
> 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:
First, many THANKS for doing this!!!!
I do agree that the components probably need some work, but I'm sure
exactly which components to have will become more clear going forward.

> 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 :).
That makes a lot of sense to me.  Is it going to get confusing as
unstable feeds into testing, and testing into stable, which unstable
we're talking about when submitting a bug against unstable?  Just a
thought.

-- 
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Xen bugzilla

[Paul Larson]

[-- Attachment #1.1: Type: text/plain, Size: 278 bytes --]

Can you make it so that bugzilla doesn't send you notification of
changes you make to your own bug?  I know I've seen this done in other
bugzillas, and just assumed it was the default.

-- 
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Xen bugzilla

[James Bulpin]

On Fri, 2005-04-22 at 21:25, Paul Larson wrote:
> Can you make it so that bugzilla doesn't send you notification of
> changes you make to your own bug?  I know I've seen this done in other
> bugzillas, and just assumed it was the default.

That is a per-user setting which look like it defaults to what you want.
I've just tried reporting a bug, then editing it myself. bugzilla
reports that it is excluding my address from the notifications.

Check your account preferences has the "Only email me reports of changes
made by other people" option checked (under prefs-email settings-global
options).

James