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 B228BDC0 for ; Wed, 5 Jun 2019 18:16:23 +0000 (UTC) Received: from mail-io1-f45.google.com (mail-io1-f45.google.com [209.85.166.45]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5A47A6D6 for ; Wed, 5 Jun 2019 18:16:23 +0000 (UTC) Received: by mail-io1-f45.google.com with SMTP id u13so20991811iop.0 for ; Wed, 05 Jun 2019 11:16:23 -0700 (PDT) To: Geert Uytterhoeven , Mark Brown References: <0bc02b84-4d9a-59a7-e6c6-a3b602adca73@linuxfoundation.org> <1018c8ba-61a0-c024-cd98-3b82ebd710ec@redhat.com> <20190602180913.GR12898@sasha-vm> <667d4900-0a9a-d6f8-7012-3c15c2df7da8@linuxfoundation.org> <20190603180953.GA17954@chatter.i7.local> <20190603211004.GU12898@sasha-vm> <20190603221131.GE2456@sirena.org.uk> <6a90bf6c-e9a4-85eb-527c-c4bc3658e779@linuxfoundation.org> <20190605092717.GK2456@sirena.org.uk> From: Shuah Khan Message-ID: <252a548a-6abe-e422-9c9a-a4d45831f244@linuxfoundation.org> Date: Wed, 5 Jun 2019 12:16:21 -0600 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Cc: ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs! List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Mark and Geert, On 6/5/19 5:48 AM, Geert Uytterhoeven wrote: > Hi Mark, > > On Wed, Jun 5, 2019 at 11:27 AM Mark Brown wrote: >> On Tue, Jun 04, 2019 at 11:16:17AM -0600, Shuah Khan wrote: >>> - Create a directory under our source tree for bugs. This way bugs >>> stay with the source and we manage them the same way we handle >>> non-runtime objects: Documenation, scripts etc. This can be flat >>> directory or have a sub-dir structure underneath. >>> >>> ../bugs similar to ../Documentation >> >> If bugs are tracked in the source tree doesn't that make it difficult >> for people to update the bugs? > Right. It would be harder for users to report bugs. Unless we com up with a way to automate the process of taking user reported generating reports that can be committed. As I was playing with git-bug, I started to think maybe we can leverage our process to keep bugs in the same repo. > Indeed. While storing the bug state with the sources sounds like a > great idea, it's far from trivial in distributed development: > - Where are bugs reported (added to git)? > In upstream, or in maintainer repos? > At least the tree where a fix is applied should carry the bug report. > - Unless downstream trees merge from upstream on a regular basis, > they won't have all reports for bugs that apply to their trees. > My thinking is that we follow the same process of keeping the repos consistent. > Closing bugs does follow the expected path, though: both fix and bug > report update move upstream through a pull request. > This is the value add for me as I proposed the idea. There are lot of logistics to consider as you both pointed out. thanks, -- Shuah