I complained and asked for answers but got ignored since last June about these weird branches stuff, nobody seemed interested in looking into what was going on. Multiple times updates simply skipped Testing branch. Stable-Staging seems to be the real Testing branch sometimes, and we get updates on Testing AFTER the Stable branch got them.
Here an example, and it was like that for three previous updates too
Or more recently, I even predicted it, and ‘warned’ about it, but still, had to wait the next day
Maybe things have to be looked at, sorted out, and clean branches update procedure put in place? Currently to me it makes no sense, looks like “amateur hour” sometimes, when I know people working on Manjaro are able to have high standards. It’s sad.
open an issue on boxit2 ?
is it possible to create pre or post send hook like git ? not too hard for an grpc tool
boxit test version branch-1 and if the version is higher then display a warning to maintainer ?
Regarding updating to Plasma 5.23, are there any issues with having certain effects enabled in 5.22.5 before the upgrade that are not part of the new Plasma? Or will those effects simply not exist afterwards and Plasma should otherwise work normally without having to know which effects to disable first? Thanks!
@ManjaroTeam: I made the last updates with the testing branch on Manjaro KDE 21.1.6. I don’t encounter problem with it. I’m using wayland under KDE plasma 5.23.2 and for now it is ok. The new version of Latte dock (0.10.3) available in the testing branch solved my issue with the floating panel (hiding it). I’m happy.
Hope to see these updates in the stable branch soon.
Yes, it is an overlay in stable-staging. Current update cycle is: Sync Arch in stable-staging, build our packages against it and pull our overlay packages from our unstable branch. Then snap it over to our testing branch. When all done, we may snap the result to stable.