> > > The changes look good to me, except for the ABI breakage in
> unitymenumodel.h
> > >
> > > Are we sure that all of its consumers are only using the QML plug-in?
> >
> > There are a few points where we used UnitMenuModel in it's C++ form, but
> only
> > as a pointer.
> > Nothing used the actionsChanged signal though.
>
> Okay, so what's the rule regarding known "okay" ABI breakages then? Is it okay
> to skip the ABI version bump in this case?
Is there an explicit ABI version? Or do you just mean bump to 0.2.8? If so, we can do that.
> > > The changes look good to me, except for the ABI breakage in
> unitymenumodel.h
> > >
> > > Are we sure that all of its consumers are only using the QML plug-in?
> >
> > There are a few points where we used UnitMenuModel in it's C++ form, but
> only
> > as a pointer.
> > Nothing used the actionsChanged signal though.
>
> Okay, so what's the rule regarding known "okay" ABI breakages then? Is it okay
> to skip the ABI version bump in this case?
Is there an explicit ABI version? Or do you just mean bump to 0.2.8? If so, we can do that.