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: Philippe Mathieu-Daudé
Subject: Re: [RFC] GitLab issue tracker labeling process: arch/target, os, and accel labels
Date: Mon, 14 Jun 2021 22:25:37 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1

On 6/14/21 8:53 PM, Philippe Mathieu-Daudé wrote:
> On 6/14/21 7:32 PM, John Snow wrote:
>>
>> # OS
>>
>> Currently "os: XXX" for BSD, Linux, Windows, and macOS.
>>
>> https://gitlab.com/qemu-project/qemu/-/labels?subscribed=&search=os%3A
>>
>> Multiple OS labels can be applied to an issue.
>>
>> Originally, we kept this label somewhat vague and have been using it to
>> identify both the host AND guest involved with an issue.
>>
>> Stefan Weil has requested that we refactor this to separate the concerns
>> so that he can identify issues where Windows is the host without wading
>> through numerous reports where Windows is merely the guest. Reasonable
>> request.
>>
>> Shall we split it into "host: XXX" and "guest: XXX" for {BSD, Linux,
>> Windows, macOS}?
> 
> I'm missing the importance of the guest OS. Either it is in pair with
> the host accel, or it is accel:TCG and I see the guest irrelevant

Err I mentioned the nested case, but generally I tend to have the same
view, guest is not very relevant (except for qemu-guest-agent maybe).

> (do we want to list all firmwares?).
> 
> So I'll let other sort this out.



reply via email to

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