From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 621D97A8 for ; Wed, 28 Jun 2017 06:59:18 +0000 (UTC) Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D85591CE for ; Wed, 28 Jun 2017 06:59:17 +0000 (UTC) Date: Wed, 28 Jun 2017 08:59:15 +0200 Message-ID: From: Takashi Iwai To: Jiri Kosina In-Reply-To: References: <1de3c642-a4b7-1065-5c35-ba32866d471d@redhat.com> <20170627175321.GS21846@wotan.suse.de> <1498588234.18166.29.camel@HansenPartnership.com> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: James Bottomley , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug reporting feedback loop List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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