On 2019-10-07 17:21:50, brendanhiggins@google.com wrote:
On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT kernel-helpdesk@rt.linuxfoundation.org wrote:
On 2019-10-02 17:53:58, brendanhiggins@google.com wrote:
Hi,
I am thinking about requesting a Bugzilla component for my kernel project KUnit. I am not sure if this is the right place for it. Some background on KUnit: We are working on adding unit testing for the Linux kernel[1][2]. We have our initial patchset that introduces the subsystem in the process of being merged (Linus sent our PR back to us for a minor fix[3], so it should be in either 5.4-rc2 or 5.5, but is nevertheless in linux-next). However, we also have a staging repo that people are using and some supporting code that lives outside of the kernel.
So I am trying to figure out:
- Is it appropriate to request a Bugzilla component before our subsystem has been merged into torvalds/master? I would just
wait, but I have some users looking to file issues, so I would prefer to provide them something sooner rather than later.
- Is it appropriate to use the kernel's Bugzilla to track issues outside of the Linux kernel? As I mention above, we have code
that lives outside of the kernel; is it appropriate to use kernel.org's Bugzilla for this?
- Does Bugzilla match my planned usage model? It doesn't look like Bugzilla get's much usage aside from reporting bugs. I want to
use it for tracking feature progress and things like that. Is that okay?
Yes, we can certainly host this on bugzilla.kernel.org. Would you be okay with Tools/KUnit as product/category?
Cool, well as long as none of my above points are an issue for you. Then yes, can you create me a component? I am fine with Tools/KUnit as the product/category.
Apologies for the delay, mostly due to Thanksgiving in Canada. You should be able to start using Tools/KUnit now. It uses a default virtual assignee tools_kunit@kernel-bugs.kernel.org, so to start receiving bugmail for it, please follow instructions on this page:
https://korg.wiki.kernel.org/userdoc/bugzilla#to_start_getting_bug_reports_f...
Best regards,
On Tue, Oct 15, 2019 at 1:14 PM Konstantin Ryabitsev via RT kernel-helpdesk@rt.linuxfoundation.org wrote:
On 2019-10-07 17:21:50, brendanhiggins@google.com wrote:
On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT kernel-helpdesk@rt.linuxfoundation.org wrote:
On 2019-10-02 17:53:58, brendanhiggins@google.com wrote:
Hi,
I am thinking about requesting a Bugzilla component for my kernel project KUnit. I am not sure if this is the right place for it. Some background on KUnit: We are working on adding unit testing for the Linux kernel[1][2]. We have our initial patchset that introduces the subsystem in the process of being merged (Linus sent our PR back to us for a minor fix[3], so it should be in either 5.4-rc2 or 5.5, but is nevertheless in linux-next). However, we also have a staging repo that people are using and some supporting code that lives outside of the kernel.
So I am trying to figure out:
- Is it appropriate to request a Bugzilla component before our subsystem has been merged into torvalds/master? I would just
wait, but I have some users looking to file issues, so I would prefer to provide them something sooner rather than later.
- Is it appropriate to use the kernel's Bugzilla to track issues outside of the Linux kernel? As I mention above, we have code
that lives outside of the kernel; is it appropriate to use kernel.org's Bugzilla for this?
- Does Bugzilla match my planned usage model? It doesn't look like Bugzilla get's much usage aside from reporting bugs. I want to
use it for tracking feature progress and things like that. Is that okay?
Yes, we can certainly host this on bugzilla.kernel.org. Would you be okay with Tools/KUnit as product/category?
Cool, well as long as none of my above points are an issue for you. Then yes, can you create me a component? I am fine with Tools/KUnit as the product/category.
Apologies for the delay, mostly due to Thanksgiving in Canada. You should be able to start using Tools/KUnit now. It uses a default virtual assignee tools_kunit@kernel-bugs.kernel.org, so to start receiving bugmail for it, please follow instructions on this page:
No worries.
https://korg.wiki.kernel.org/userdoc/bugzilla#to_start_getting_bug_reports_f...
Thanks!
On Tue, Oct 15, 2019 at 1:14 PM Konstantin Ryabitsev via RT kernel-helpdesk@rt.linuxfoundation.org wrote:
On 2019-10-07 17:21:50, brendanhiggins@google.com wrote:
On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT kernel-helpdesk@rt.linuxfoundation.org wrote:
On 2019-10-02 17:53:58, brendanhiggins@google.com wrote:
Hi,
I am thinking about requesting a Bugzilla component for my kernel project KUnit. I am not sure if this is the right place for it. Some background on KUnit: We are working on adding unit testing for the Linux kernel[1][2]. We have our initial patchset that introduces the subsystem in the process of being merged (Linus sent our PR back to us for a minor fix[3], so it should be in either 5.4-rc2 or 5.5, but is nevertheless in linux-next). However, we also have a staging repo that people are using and some supporting code that lives outside of the kernel.
So I am trying to figure out:
- Is it appropriate to request a Bugzilla component before our subsystem has been merged into torvalds/master? I would just
wait, but I have some users looking to file issues, so I would prefer to provide them something sooner rather than later.
- Is it appropriate to use the kernel's Bugzilla to track issues outside of the Linux kernel? As I mention above, we have code
that lives outside of the kernel; is it appropriate to use kernel.org's Bugzilla for this?
- Does Bugzilla match my planned usage model? It doesn't look like Bugzilla get's much usage aside from reporting bugs. I want to
use it for tracking feature progress and things like that. Is that okay?
Yes, we can certainly host this on bugzilla.kernel.org. Would you be okay with Tools/KUnit as product/category?
Cool, well as long as none of my above points are an issue for you. Then yes, can you create me a component? I am fine with Tools/KUnit as the product/category.
Apologies for the delay, mostly due to Thanksgiving in Canada. You should be able to start using Tools/KUnit now. It uses a default virtual assignee tools_kunit@kernel-bugs.kernel.org, so to start receiving bugmail for it, please follow instructions on this page:
No worries.
https://korg.wiki.kernel.org/userdoc/bugzilla#to_start_getting_bug_reports_f...
Thanks!
linux-kselftest-mirror@lists.linaro.org
-
Brendan Higgins -
brendanhiggins＠google.com via RT -
Konstantin Ryabitsev via RT