On Wed, May 28, 2025 at 1:14 PM Nate Graham <n...@kde.org> wrote: > On 5/26/25 7:13 AM, David Redondo wrote: > > Am Montag, 26. Mai 2025, 13:52 schrieb Martin Riethmayer: > >> Hi all, > >> [...] > >> 1.) Do a "no-string-changed-bugix" release for .6 > >> Pro: > >> - should not have any issue with extra branching > >> - consistent with released schedule (not super important, probably) > >> Con: > >> - Hard to enforce / communicate > >> - bound to fail sooner or later > >> - Problematic for CI > > > > I don't understand why it should be hard to enforce? > > String changes are forbidden anyways in stable releases. > > > > What is bound too fail there? What are the problems for CI? > > > > If there are really problems we need to look into them instead of > > catch-all phrases that say nothing. > > Agreed. We can do bugfix releases with no translation changes, that's fine. > > If there are additional technical challenges, we should work on solving > them, because in principle, we need to be able to have two stable > branches in flight simultaneously. If we can't do that, then we won't be > able to move beyond a world where each Plasma version is unmaintained > the moment the next one is released. >
That can be worked on, if we could make sure that we have identified and resolved everything before the releases start to happen that would be great. Mainly so we can avoid having to run around fixing things because they're broken and the situation is somewhat urgent. One item I will raise - currently unit tests within various parts of Plasma are broken on stable branches due to bad interactions surrounding sdk/selenium-webdriver-at-spi. This is caused by sdk/selenium-webdriver-at-spi not being part of Plasma, yet having a dependency on KWin. That essentially causes a runtime dependency loop that results in the wrong versions of software being used. Short of rewriting sdk/selenium-webdriver-at-spi to use a non-KDE window manager, the only fix I can see is moving it to be part of Plasma. > > Nate > > Cheers, Ben
