qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] GitLab issue tracker labeling process: arch/target, os, and ac


From: David Gibson
Subject: Re: [RFC] GitLab issue tracker labeling process: arch/target, os, and accel labels
Date: Wed, 16 Jun 2021 14:38:37 +1000

On Tue, Jun 15, 2021 at 03:56:46PM +0200, Philippe Mathieu-Daudé wrote:
> On 6/15/21 4:08 AM, David Gibson wrote:
> > On Mon, Jun 14, 2021 at 01:32:11PM -0400, John Snow wrote:
> > In general, what's the convention when a bug is independent of (say)
> > the accel: does it get none of the accel tags, or all of them?
> > Likewise with OS and the other categories.
> 
> None: remove the label. Otherwise you'll notify everybody subscribed
> to specific labels.
> 
> >> We probably want to keep a set of labels that apply to the host
> >> architecture. These are useful for build failures, environment setup 
> >> issues,
> >> or just documenting the exact environment on which an issue was observed.
> > 
> > Ah.. that's another general question.  Are the labels supposed to
> > document where the problem has been definitely observed, or a best
> > estimate at where it will appear.  It would be very common for a bug
> > to be observed initially on only one, but quickly turn out to be
> > independent of host and/or target arch.
> 
> Similar. If the problem is generic, remove the specific labels.
> 
> Regards,
> 
> Phil.


Understood, thanks.

-- 
David Gibson                    | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au  | minimalist, thank you.  NOT _the_ _other_
                                | _way_ _around_!
http://www.ozlabs.org/~dgibson

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]