!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

218 Members
59 Servers

Load older messages


SenderMessageTime
5 Oct 2024
@outfoxxed:outfoxxed.meoutfoxxed personally I don't need to get this in before the release, since at least most of my users are on unstable so I'll go with whatever 08:07:10
@k900:0upti.meK900Anyway I guess we'll have to see how this cycle goes08:07:44
@k900:0upti.meK900And then we can see what we do about the next one08:07:51
@outfoxxed:outfoxxed.meoutfoxxedif we're doing 6.7 in 24.11 maybe it makes sense to merge the patch anyway for all the kde users, and rebase it for 6.8 when thats ready?08:08:06
@k900:0upti.meK900Because right now this cycle is going like this08:08:09
@k900:0upti.meK900image.png
Download image.png
08:08:11
@outfoxxed:outfoxxed.meoutfoxxed
In reply to @outfoxxed:outfoxxed.me
if we're doing 6.7 in 24.11 maybe it makes sense to merge the patch anyway for all the kde users, and rebase it for 6.8 when thats ready?
if not ill wait till 6.8 to fix the nits and rebase
08:09:01
@k900:0upti.meK900The problem is we don't know if we're doing 6.7 or 6.8 before we try 6.808:09:35
@outfoxxed:outfoxxed.meoutfoxxedah are you testing for application correctness or just that everything builds08:10:04
@k900:0upti.meK900Mostly the former08:10:13
@k900:0upti.meK900Hydra can take care of the latter08:10:17
@k900:0upti.meK900But with e.g. 6.7.3 people are reporting weird runtime crashes08:10:26
@k900:0upti.meK900That I personally haven't hit but there's a lot of talk in the Plasma rooms08:10:41
@outfoxxed:outfoxxed.meoutfoxxedtheres lots of nasty ones in quick08:10:42
@outfoxxed:outfoxxed.meoutfoxxedhit them personally a fair bit08:10:51
@k900:0upti.meK900And that's not something Hydra can catch08:10:56
@outfoxxed:outfoxxed.meoutfoxxedpersonally would probably just hold off on 6.8 unless plasma can actually be fully tested in that time08:11:49
@k900:0upti.meK900If we get 6.8 into the next cycle and it goes closer to a normal timeline (i.e. 1-1.5 weeks and not 3), we'll have over a month to release08:13:12
@k900:0upti.meK900And we'll definitely have at least one more cycle to revert to 6.7 if it's really ba08:13:23
@k900:0upti.meK900* And we'll definitely have at least one more cycle to revert to 6.7 if it's really bad08:13:24
@outfoxxed:outfoxxed.meoutfoxxedprobably good enough then08:13:36
@k900:0upti.meK900But if it goes for 3 weeks, we'll have maybe two weeks to last possible revert point08:14:32
@k900:0upti.meK900And that's going to suck08:14:39
@k900:0upti.meK900I guess one thing we have going for us is that there's other distros08:14:59
@k900:0upti.meK900That don't need two weeks to ship a Qt update08:15:12
@outfoxxed:outfoxxed.meoutfoxxed please beta test, arch 🙏 08:15:17
@k900:0upti.meK900So we may have a rough baseline for 6.8 from that08:15:29
@outfoxxed:outfoxxed.meoutfoxxedis that two weeks worth of qt rebuilds or just having to fit that in a staging cycle08:15:58
@k900:0upti.meK900Or maybe I'm overthinking all of this and Randy just killed it on the Darwin stdenv rewrite and it'll go smoothly and we will not have problems08:16:14
@k900:0upti.meK900
In reply to@outfoxxed:outfoxxed.me
is that two weeks worth of qt rebuilds or just having to fit that in a staging cycle
The overall staging cycle
08:16:20

Show newer messages


Back to Room ListRoom Version: 9