RE: Bug tracking system

RE: Bug tracking system

[Ian Pratt]

> >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?

Thanks,
Ian

Re: Bug tracking system

[Nivedita Singhvi]

Ian Pratt 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.
> 
> 
> 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'd like to vote for earlier rather than later - because there
seem to be a few things that we are running into, and not everything
is getting posted to list, which is a bit of a concern, especially
the less severe and the once-off stuff. It would be easier to search
thru a buglist rather than mailarchives to find a report of a problem.

I started keeping a list this week:

1. Spurious oops (I just posted this earlier)
2. Dom1 silently hung (only ran a man cmd)
3. Dom1 hung on a large ping send (approx 16700 bytes)
4. raw netperf pkts seem to be not working (possible app bug)
    (orig run into by jonm)
    from domU to dom0
5. xend failed to start (various causes)
6. dom0 network script fails to set up bridge/interfaces
    (originally hit by paull) - this one just needs error handling,
    have fix, not waiting long enough sometimes.
7. xm create -c failed to start up console (last night on 4/12 build
    but it was 2:00AM and I didn't investigate further)
8. fails to boot (kernel config options)

Stopping to repro and investigate is slowing down the 
implementation/testing fronts.


thanks,
Nivedita

6.

> 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
> 
> 

RE: Bug tracking system

[Anthony Liguori]

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

Re: Bug tracking system

[Paul Larson]

Anthony Liguori wrote:

>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,
>  
>
Wikis are nice and simple but have a few obvious problems:
1. It can quickly become cumbersome for more than a handful of bugs
2. doesn't encourage details to be submitted along with the bug report
(you're likely to get a lot of one-liner's that only the submitter
understands how to reproduce)
3. remember that if it's not the final solution, it'll have to be
transferred to the new one

What is appealing about Trac that made you want to use it?  Is there
something you like about trac in particular, or hate about bugzilla?
I've noticed that a lot of people tend to customize bugzilla, so I know
that a lot of gripes can be overcome.  If it's really a concern, then it
might be better to go with bugzilla from the start rather than trying to
transfer everything later.  Personally I don't have a preference as long
as there's some system available to keep things from falling through the
cracks.

Thanks,
Paul Larson

Re: Bug tracking system

[Ryan Harper]

* 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

Bug tracking system

[Ralf Baechle]

While I'm tinkering with the system - linux-mips.org still has no
bug tracking system to track bugs and so issues get forgotten also the
only system we have to track feature requests and other to-do items
currently is the to do page in the wiki.  But the wiki isn't the best
medium for this purpose.  So should we install something like bugzilla -
which I personally never liked - or other tracking system?  Suggestions?

  Ralf

Re: Bug tracking system

[James Hogan]

On 14/08/14 15:55, Ralf Baechle wrote:
> While I'm tinkering with the system - linux-mips.org still has no
> bug tracking system to track bugs and so issues get forgotten also the
> only system we have to track feature requests and other to-do items
> currently is the to do page in the wiki.  But the wiki isn't the best
> medium for this purpose.  So should we install something like bugzilla -
> which I personally never liked - or other tracking system?  Suggestions?

If bugzilla is to be used, would it make sense to use the kernel.org
bugzilla which already has a MIPS category, rather than setting up a new
one?

https://bugzilla.kernel.org/buglist.cgi?product=Platform%20Specific%2FHardware&component=MIPS&resolution=---

Cheers
James

Re: Bug tracking system

[James Hogan]

On 14/08/14 15:55, Ralf Baechle wrote:
> While I'm tinkering with the system - linux-mips.org still has no
> bug tracking system to track bugs and so issues get forgotten also the
> only system we have to track feature requests and other to-do items
> currently is the to do page in the wiki.  But the wiki isn't the best
> medium for this purpose.  So should we install something like bugzilla -
> which I personally never liked - or other tracking system?  Suggestions?

If bugzilla is to be used, would it make sense to use the kernel.org
bugzilla which already has a MIPS category, rather than setting up a new
one?

https://bugzilla.kernel.org/buglist.cgi?product=Platform%20Specific%2FHardware&component=MIPS&resolution=---

Cheers
James

Re: Bug tracking system

[Ralf Baechle]

On Thu, Aug 14, 2014 at 04:09:26PM +0100, James Hogan wrote:

> On 14/08/14 15:55, Ralf Baechle wrote:
> > While I'm tinkering with the system - linux-mips.org still has no
> > bug tracking system to track bugs and so issues get forgotten also the
> > only system we have to track feature requests and other to-do items
> > currently is the to do page in the wiki.  But the wiki isn't the best
> > medium for this purpose.  So should we install something like bugzilla -
> > which I personally never liked - or other tracking system?  Suggestions?
> 
> If bugzilla is to be used, would it make sense to use the kernel.org
> bugzilla which already has a MIPS category, rather than setting up a new
> one?
> 
> https://bugzilla.kernel.org/buglist.cgi?product=Platform%20Specific%2FHardware&component=MIPS&resolution=---

Indeed why not.  Might even talk to the kernel.org admins to have it show
up as bugzilla.linux-mips.org or something like that.

I personally like the Debian bug tracking system but I'm not sure how
well it integrates with esotheric MTAs such as zmailer and how bad spam
issues would be.

  Ralf

Bug tracking system

[Paul Larson]

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

There was some discussion some time ago about a bug tracking system for
Xen.  Is there any plan on when that will be available?
-- 
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