All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jiri Kosina <jikos@kernel.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug reporting feedback loop
Date: Wed, 28 Jun 2017 08:59:15 +0200	[thread overview]
Message-ID: <s5hd19ovbr0.wl-tiwai@suse.de> (raw)
In-Reply-To: <alpine.LSU.2.20.1706280033050.30709@cbobk.fhfr.pm>

On Wed, 28 Jun 2017 00:35:40 +0200,
Jiri Kosina wrote:
> 
> On Tue, 27 Jun 2017, James Bottomley wrote:
> 
> > So I think it would be a useful service for distro's to provide a 
> > release of -next that users can try.  Perhaps it doesn't have to be 
> > daily, but at least weekly would be enormously helpful.
> 
> We do:
> 
> 	https://build.opensuse.org/repositories/Kernel:linux-next
> 
> But we are getting close to zero bugreports against it. Which either means 
> it's very rarely used (and therefore we should perhaps be more vocal about 
> it), or people who are educated enough to use it are actually educated 
> enough to report any issues directly upstream.

IMO, we should consider deploying more CI tests (either openQA or
simplified ones) for KOTD and linux-next.  I discussed with out QA
guys once, but it's not really happening yet.


thanks,

Takashi

  reply	other threads:[~2017-06-28  6:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 22:34 [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug reporting feedback loop Laura Abbott
2017-06-22 12:36 ` Jiri Kosina
2017-06-27 17:53   ` Luis R. Rodriguez
2017-06-27 18:26     ` Laurent Pinchart
2017-06-27 18:30     ` James Bottomley
2017-06-27 18:41       ` Daniel Vetter
2017-06-27 19:02       ` Luis R. Rodriguez
2017-06-27 19:46         ` Guenter Roeck
2017-06-28 10:19           ` Mark Brown
2017-06-27 22:35       ` Jiri Kosina
2017-06-28  6:59         ` Takashi Iwai [this message]
2017-06-27 18:31     ` Takashi Iwai
2017-06-27 19:04       ` Luis R. Rodriguez
2017-06-28  8:04         ` Daniel Vetter
2017-06-22 14:08 ` Takashi Iwai
2017-06-22 14:12   ` Jiri Kosina
2017-06-22 14:24     ` Takashi Iwai
2017-06-28 13:12       ` Jani Nikula
2017-06-28 13:13         ` Takashi Iwai
2017-06-22 15:34 ` James Bottomley
2017-06-23 14:52 ` Greg KH
2017-06-23 20:28   ` Jiri Kosina
2017-06-25 17:11   ` Laura Abbott

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hd19ovbr0.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jikos@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.