Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug reporting feedback loop

[Daniel Vetter <daniel.vetter@ffwll.ch>]

On Tue, Jun 27, 2017 at 9:04 PM, Luis R. Rodriguez <mcgrof@kernel.org> wrote:
>> I guess it shouldn't be too difficult to build a kernel package based
>> on subsystem for-next branch regularly like we do for KOTD and
>> linux-next kernel packages.  You'd need to set up some cron job to git
>> pull, repackage tarball and adjust config file somehow automatically,
>> then feed it to osc (in the case of openSUSE/SUSE OBS).
>
> That'd be great. It sounds like we have trees like this for media, and
> wireless. Not sure of others.

In case anyone cares, I'm trying to make drm-tip _the_ integration
tree for graphics. Doesn't contain everything yet, but generally a
good place for build-bots, and iirc at least ubuntu has a ppa for it:

https://cgit.freedesktop.org/drm-tip

And the integration manifest:

https://cgit.freedesktop.org/drm-tip/tree/integration-manifest

Probably the neatest thing is that there's no single person
maintaining it, but conflicts get resolved and stored when they
happen, by the person who pushes the patches creating the conflict.
See

https://cgit.freedesktop.org/drm-tip/log/?h=rerere-cache

So yeah we've managed to scale maintaining an integration tree to a
team of 20+ people, everyone with commit rights in the various trees
essentially :-)

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch