Care and feeding of downstreams

[Kevin DuBois]

As for the Display changes, the branch is/was here:
https://code.launchpad.net/~kdub/qtmir/display-groups

It seems sensible to me that the mir team should keep around a list (google
docs maybe?) of the branches that fix the downstreams. If in the review
process, we find that a change breaks the downstream, maybe we should wait
to land that branch until the downstreams have a fix. This would make it
easier for the release-designate come release time, as well as anyone
trying to tinker with the whole stack against lp:mir.

On Fri, Mar 6, 2015 at 5:04 AM, Alan Griffiths <alan.griffiths at canonical.com
> wrote:

> On 06/03/15 09:57, Daniel van Vugt wrote:
> > "failing to build against lp:mir" I mean.
>
> Point taken.
>
> We should automate this check.
>
> >
> >
> > On 06/03/15 17:55, Daniel van Vugt wrote:
> >> Hi all,
> >>
> >> The following branches are failing to build right now. Could the owners
> >> of the respective changes please look into the issues?
> >>
> >> lp:qtmir/devel-mir-next
> >>    kdub: Display class changes (still calling flip())
> >>    racarr: keymap_changed()
> >>
> >> lp:unity-system-compositor/devel-mir-next
> >>    racarr: spinner/eglapp.c needs buffer stream (copy from lp:mir?)
> >>    alan_g: mir/time/timer.h missing
>
> OTOH I don't deserve credit for AlbertA's work.
>
> >>    alan_g: FocusController changed
> >>
> >> There may be more build failures hiding behind those ones...
> >>
> >> - Daniel
> >
>
>
> --
> Mir-devel mailing list
> Mir-devel at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/mir-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/mir-devel/attachments/20150310/b1b2172e/attachment.html>