Fedora 40 Release Thread: Important for
Fedora 40 Release Thread: Important for all approvers! (Will file issue in github after discussion)
JAlright, we have three things in flight that will conflict so we're going to have to go in order.
J1) F40 enable goes first, @bsherman will merge to unblock the other two, we are still waiting on confirmation from timothee on the final image names, so even though he is merging, the images WILL PROBABLY BE RENAMED so if you decide to yolo yourself onto F40 you are on your own if you're not paying attention
BJ2) HWE deconflicting - this has served us well and has gotten us an awesome relationship with Framework and other interested parties. Now it's time to trim it down
J3) ARM images - RJ got a mac but was kind enough to not give into the shiny light, once we've gotten the first two items done this should go way smoother.
JLet's try to get these in order because if we go the other way it will suck worse.
JThat leaves ISOs to further discuss, but those seem well in hand and what we have now is "good enough" but offline flatpaks would be awesome, plenty of time.
JANYTHING ELSE FOR FEDORA 40?
JIt's past free practice and qualifying, everything not bolted down should either be sunset or archived, let's go into GA with as little technical debt as possible.
J(Anything not on this list won't be brought forward into F40, so old experiments and repos will remain at the version they are and naturally fall out of support)
BJthank you, cramped plane typing isn't fun lol
ROn the F40 naming, I've added my thoughts to the PR and approved.
In short, I vote for keeping what we have for now, and switching as soon as we find out upstream's naming convention.
Then later we decide if we will maintian the old image names or not (I don't think we should).
In short, I vote for keeping what we have for now, and switching as soon as we find out upstream's naming convention.
Then later we decide if we will maintian the old image names or not (I don't think we should).
JLooks like we've got skew in main
J@Kyle Gospo got time to take a look?
KOut on a walk but I can take a look soon
Jack
RIsn't it the usual RPMFusion issues that work themselves out over time, without us needing to do anything?
KAye, that looks like it
Jyeah, I still can't tell from the output
Jwe could turn it off, file the issue and then revisit since it's the only one?
Japtx is useful af. 
RSorry, not sure what you mean by "turn it off". Failing builds are currently all F40 images, but were building successfully the last run.
If we simply merge now, it will pass when RPMFusion and Fedora provide compatible packages. Until then, it'll fail
If we simply merge now, it will pass when RPMFusion and Fedora provide compatible packages. Until then, it'll fail
Jno I mean not do the aptx packge
Jor would we need to special case f40?
BI expect F40 to fail a lot between now and launch. That’s the other reason to not stress about preview builds
Kyep, let it fail
BWe can merge and let it fail
Jok so want me to merge it?
JON IT
Jold on
Jhold on
Jlet me say what @bsherman wanted to say
J"you wanted F40, here you go."
J"but it doesn't work"
J"I know."
BThanks @j0rge you get me
RWill prep the Bluefin PR, but there's other dependencies that we will be waiting for, like blur-my-shell hasn't got F40 building
K"damn bro that's crazy, happy for you or sorry to hear that, whatever"
Jbluefin is always one behind, I ain't sweating 40
JI'm more worried about the 99 other things ahead of it, hahaha
RI'm more worried about the 99 other things ahead of itLooking at your list, I don't think there's any show-stoppers except for that F40 build. HWE is a DevExp change that can happen at any point? It should be invisible to end users as I assume the image names will remain the same.
Joh I meant the other bluefin parts
Janything else for tonight from this hitlist?
RARM and Aarch is way over my head, so I'll leave that to the people who know what they're doing.
Can't think of anything else.
Can't think of anything else.
BWho asked for bluefin or bazzite f40? If we are talking about doing all that. We should just hold this whole thing
RHow so?
I thought the next steps on the F40 builds would be enabling it in the downstream images, right? Why should we hold?
I thought the next steps on the F40 builds would be enabling it in the downstream images, right? Why should we hold?
Jwe were thinking main first for all of this
Jlike, 1,2,3 for main
Jthen down the line
