Received: by 10.192.165.148 with SMTP id m20csp2193048imm; Thu, 3 May 2018 12:00:06 -0700 (PDT) X-Google-Smtp-Source: AB8JxZobU2D5AiFbXYId7Wropl1mcBS6Xh3C1JRzU7mCElPFcJkOTMPKxy9c11UehznUZBbX5STr X-Received: by 10.98.16.131 with SMTP id 3mr985860pfq.229.1525374006130; Thu, 03 May 2018 12:00:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525374006; cv=none; d=google.com; s=arc-20160816; b=V0xbJ40/HgY/7N3fAep8qSThsLjQLmCd01HYcSVCI6uviq3Kr6j6UWULTMR1BO21uX M9WfQ5gG5UKIXXBMZqIid0aGWL9iNTdmXi7XcPHo8Im2hYNbhx5YOShvykqsY5rquwFX EfabB5V19Wb8ZaQDA7Hf4wCCZ0pVIaA3RbirUGUuAmhPh9n11pxZ8Qk8BrMR+bEVFF7m sPdDbXbgqnza//aBaparuRh8ahTBpECvag73thS+ZL0TPFFeGFL7IZqh6yEmOGI5VRpj i3aiWgfjjXBEji8IZkES9zdG0Iw492XRu6VvHn7s8xLdw7LiPfWtLGYm2VtjTkJC98EQ l3Nw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=/cmkmPl7eoWA/NRQa5WivUynFmQtIlTGgrUVIe1+yUI=; b=qE5ZLNnLhZCoToO/EUiV6tyAVy7eG0LyHFDU5p0/uoGw1f9K5HkIOafhFfHhZQjTAg N1vvyMWI5OET9OtpCYRmDI23haCxOWel2GVL+oHrfS2hk4zUAoSJ0T1ij+4XtQN3fom/ BIzennbolx6SxD+EETqVsNGHZcCnItynR3AI56ymY2NKDo5DDlZikEUHfjN7oO+ENTtM eQQF0EVboB6WE+OWNHR8o06LADO8g0xJFNDBnnWg9aUL3U6fiqNOiaf7m1yyh1hVxenN qsrt+ayAHgmpJWlCP526QiUyZSWA6Mn6xcYjlHKomhYbJzdfE7os6K0Yw6F0Mrcdaesl j/sw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@thunk.org header.s=ef5046eb header.b=D+Nxoctb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a14-v6si14331617plt.484.2018.05.03.11.59.51; Thu, 03 May 2018 12:00:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@thunk.org header.s=ef5046eb header.b=D+Nxoctb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751552AbeECS7Y (ORCPT + 99 others); Thu, 3 May 2018 14:59:24 -0400 Received: from imap.thunk.org ([74.207.234.97]:59278 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751582AbeECS6k (ORCPT ); Thu, 3 May 2018 14:58:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org; s=ef5046eb; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=/cmkmPl7eoWA/NRQa5WivUynFmQtIlTGgrUVIe1+yUI=; b=D+Nxoctb+cl3UabBT0DM1WN4gD 54cwbYai945MSQ2467tcbLZeyAm3WujMK+kRyB90RWfC7qKmNn0TgwvERQUO1xDs6Gx2jA2PbVCLd wKDKtd7uczSvx56ntQqUNgBHt0GqQcFYEAJ4VaT9vJgqjb+NsUo8bvK9eXX2PyiWDV8g=; Received: from root (helo=callcc.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.89) (envelope-from ) id 1fEJQz-0002gv-Dx; Thu, 03 May 2018 18:58:29 +0000 Received: by callcc.thunk.org (Postfix, from userid 15806) id 4919D7A4B0A; Thu, 3 May 2018 14:58:28 -0400 (EDT) Date: Thu, 3 May 2018 14:58:28 -0400 From: "Theodore Y. Ts'o" To: Jani Nikula Cc: Sasha Levin , Greg KH , "linux-kernel@vger.kernel.org" , "w@1wt.eu" , "ksummit-discuss@lists.linuxfoundation.org" Subject: Re: [Ksummit-discuss] bug-introducing patches Message-ID: <20180503185828.GG29205@thunk.org> Mail-Followup-To: "Theodore Y. Ts'o" , Jani Nikula , Sasha Levin , Greg KH , "linux-kernel@vger.kernel.org" , "w@1wt.eu" , "ksummit-discuss@lists.linuxfoundation.org" References: <20180501163818.GD1468@sasha-vm> <20180501194450.GD10479@thunk.org> <20180501200019.GA7397@sasha-vm> <20180501205448.GE10479@thunk.org> <877eol808s.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <877eol808s.fsf@intel.com> User-Agent: Mutt/1.9.5 (2018-04-13) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 03, 2018 at 02:08:51PM +0300, Jani Nikula wrote: > On Tue, 01 May 2018, "Theodore Y. Ts'o" wrote: > > Post -rc3 or -rc4, in my opinion bug fixes should wait until the next > > merge window before they get merged at all. > > What are -rc5 and later for then if not bug fixes? Baffled. Regression fixes? Note that if people stopped introducing regressions to the kernel, we might actually be able to release the final version after -rc6 or even earlier. There's nothing which says that we MUST have -rc7, -rc8, -rc9 releases. If we were actually disciplined in our testing and in what we push into Linus's tree, we might actually be able to go to a two-month release cycle, or perhaps even slightly shorter. But if people insist on trying to fix bugs, and those bugs fixes introduce regressions, then we end up with a longer release cycle, which causes people to want to stuck more bug fixes, or worse, even some feature commits late into the development cycle, and it becomes a vicious cycle with releases taking longer and longer. - Ted