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 1DF99D6B for ; Fri, 7 Sep 2018 21:39:59 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BA2D4A8 for ; Fri, 7 Sep 2018 21:39:58 +0000 (UTC) Date: Fri, 7 Sep 2018 18:39:46 -0300 From: Mauro Carvalho Chehab To: Linus Torvalds Message-ID: <20180907183946.6502f100@coco.lan> In-Reply-To: References: <20180904201620.GC16300@sasha-vm> <20180905101710.73137669@gandalf.local.home> <20180907004944.GD16300@sasha-vm> <20180907014930.GE16300@sasha-vm> <20180907145437.GF16300@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Cc: ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug-introducing patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Em Fri, 7 Sep 2018 09:17:18 -0700 Linus Torvalds escreveu: > On Fri, Sep 7, 2018 at 8:52 AM Linus Torvalds > wrote: > And for maintainers, it can be the exact reverse. In Vancouver Greg > said that normally, for him, the merge window is when he can take a > break, because the bulk of his work is the "leading up to merge > window" time, since that's when he works with people to set up the > branches for the next merge window. That's exactly what I do here :-) During the merge window, I usually take off my maintainer's hat and I either do some usespace stuff or do some development myself. It is not uncommon that, whatever I'm doing during the merge window would require part of the -rc1 week to finish. So, typically, fixes start being merged during -rc2 week, meaning that they'll reach upstream by -rc3 week or later. =46rom subsystem developer's side, what I notice from my chair is that most people developing new features work to cope with the Kernel=20 merging cycle, meaning that they do their testing and development focused on getting their stuff merged up to the -rc6 week. The=20 vast majority of pull requests I receive are sent during the -rc6 week. Most of the bug fixes we have actually are discovered from people are working on new stuff. Ok, pure bug reports (and fixes) can be merged anytime, but, due to the core developer's working cycle, in practice that means that I receive more bug fixes (both critical and non-critical) late at the -rc cycle. Thanks, Mauro