<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 27, 2021 at 6:10 PM Vlad Zahorodnii <<a href="mailto:vlad.zahorodnii@kde.org">vlad.zahorodnii@kde.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 8/26/21 9:58 PM, Ben Cooksley wrote:<br>
> On Wed, Aug 25, 2021 at 9:58 PM Vlad Zahorodnii <<a href="mailto:vlad.zahorodnii@kde.org" target="_blank">vlad.zahorodnii@kde.org</a> <br>
> <mailto:<a href="mailto:vlad.zahorodnii@kde.org" target="_blank">vlad.zahorodnii@kde.org</a>>> wrote:<br>
> <br>
> Hi,<br>
> <br>
> <br>
> Hi Vlad,<br>
> <br>
> <br>
> I've just merged a patch that tweaks some protocol additions in the<br>
> plasma window management protocol that were made this month and haven't<br>
> been released yet.<br>
> <br>
> Even though that change won't affect users running stable version of<br>
> plasma, it may cause issues on developer machines.<br>
> <br>
> If you experience startup issues with plasma on wayland, in particular<br>
> plasma not starting at all, please recompile the following projects:<br>
> <br>
> * plasma-wayland-protocols<br>
> * kwayland<br>
> * kwayland-server<br>
> * kwin<br>
> * plasma-workspace<br>
> <br>
> <br>
> I'm afraid the CI system may disagree with you regarding the impact on <br>
> stable branches, please see <br>
> <a href="https://build.kde.org/view/Failing/job/Plasma/job/kwayland/" rel="noreferrer" target="_blank">https://build.kde.org/view/Failing/job/Plasma/job/kwayland/</a> <br>
> <<a href="https://build.kde.org/view/Failing/job/Plasma/job/kwayland/" rel="noreferrer" target="_blank">https://build.kde.org/view/Failing/job/Plasma/job/kwayland/</a>><br>
> These breakages look to be related to plasma-wayland-protocols.<br>
> <br>
> I also note that these changes caused substantial disruption to the CI <br>
> system requiring multiple Dependency Builds to be run to correct the <br>
> issue and restore normal service.<br>
> <br>
> As plasma-wayland-protocols is not part of either Frameworks or Plasma, <br>
> please ensure necessary changes to it are landed well in advance of <br>
> starting to use them - rather than all at the same time.<br>
<br>
The issue is that Frameworks and Plasma builds break even if <br>
plasma-wayland-protocols changes land in advance.<br></blockquote><div><br></div><div>You have to land changes a week in advance for the Dependency Builds to pick them up on their normal cadence.</div><div>Depending on timing you may be able to land them earlier, but there is no guarantee as the builds are run on a staggered basis by Jenkins.<br></div><div><br></div><div>That brings the disruption caused by this to 6 Dependency Builds (two for Frameworks, four for Plasma)<br></div><div><br></div><div>Please note you also have to arrange for a release of plasma-wayland-protocols as that is part of Extragear.</div><div>This needs to be done before the next Frameworks release.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> <br>
> Sorry for the inconvenience,<br>
> Vlad<br>
> <br>
> <br>
> Thanks,<br>
> Ben<br>
<br></blockquote><div><br></div><div>Cheers,</div><div>Ben<br></div></div></div>