Am 09.01.25 um 17:20 schrieb Volker Krause:
On Donnerstag, 9. Januar 2025 11:12:09 Mitteleuropäische Normalzeit David
Redondo wrote:
Am Mittwoch, 8. Januar 2025, 17:18 schrieb Nicolas Fella:
Am 08.01.25 um 10:57 schrieb David Redondo:
Hi,
the original plan for Plasma 6.3 was to require Qt 6.8 (as the wiki
currently notes). However FreeBSD so far didn't gain Qt 6.7 and we
never bumped it. The first Beta is tomorrow. So I think we just go with
6.7?
David
I am rather annoyed that this is the second (at least) time we find
ourselves in this situation. Can we somehow handle this better in the
future?
I agree we had the same situation with Plasma 6.1 where we wanted
6.7 but were stuck on 6.6 leading to the
"6.6 (6.7 strongly recommended) " minimum.
Maybe we did not communicate appropriately with sysadmin about this and
our wish was not known? Or is there something else holding it back?
Independent of this specific case, I don't think expecting sysadmin (ie
practically just Ben as far as CI is concerned) to deal with dependency
updates on the CI is going to scale, we need to see that as our all
responsibility. And since the move away from Jenkins a lot of that work can be
done without special sysadmin powers:
* Figure out if upstream has the new version already, and if not figure out
what's blocking that (and outside of Linux/FreeBSD upstream is also us, via
Craft).
* Submit MRs for the CI pieces that need updating (container images, Gitlab
template).
* And probably most importantly: help with dealing with the potential fallout
form the updates.
Regards,
Volker
I think this particular case is mostly a FreeBSD issue, which happens to
be where contributing to our CI setup is the least approachable for
people on the outside.
