From: "firstname.lastname@example.org via RT" <email@example.com>
To: unlisted-recipients:; (no To-header on input)
Cc: firstname.lastname@example.org, email@example.com
Subject: Re: [Kernel.org Helpdesk #80110] Bugzilla Component for KUnit?
Date: Wed, 16 Oct 2019 17:05:59 -0400 [thread overview]
Message-ID: <rt-4.4.0-13264-1571259959-1468.80110-6-0@linuxfoundation> (raw)
On Tue, Oct 15, 2019 at 1:14 PM Konstantin Ryabitsev via RT
> On 2019-10-07 17:21:50, firstname.lastname@example.org wrote:
> > On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT
> > <email@example.com> wrote:
> > >
> > > On 2019-10-02 17:53:58, firstname.lastname@example.org 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. 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, 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:
> > > >
> > > > 1. 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.
> > > >
> > > > 2. 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?
> > > >
> > > > 3. 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 email@example.com, so to start receiving bugmail for it, please follow instructions on this page:
prev parent reply other threads:[~2019-10-16 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-80110@linuxfoundation>
2019-10-02 21:53 ` Bugzilla Component for KUnit? Brendan Higgins
2019-10-04 18:55 ` [Kernel.org Helpdesk #80110] " Konstantin Ryabitsev via RT
2019-10-07 21:21 ` Brendan Higgins
2019-10-07 21:21 ` firstname.lastname@example.org via RT
2019-10-15 2:41 ` Brendan Higgins
2019-10-15 2:42 ` email@example.com via RT
[not found] ` <rt-4.4.0-14627-1570483310-1693.80110-6-0@linuxfoundation>
2019-10-15 20:14 ` Konstantin Ryabitsev via RT
2019-10-16 21:05 ` Brendan Higgins
2019-10-16 21:05 ` firstname.lastname@example.org via RT [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).