Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!

[Shuah Khan <skhan@linuxfoundation.org>]

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 <broonie@kernel.org> 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