we could do some documentation for it but i feel like users would be a bit scared to press the butto
we could do some documentation for it but i feel like users would be a bit scared to press the button
�ill remove the huge X in my merge request
�done
Jyeah purge all that stuff!
JMan, flight to Tirana was cancelled, no LAS for me. 
RPlease can I have an ack
https://github.com/ublue-os/main/pull/812
Will work on the config over the weekend to hopefully prevent it from getting stuck again
https://github.com/ublue-os/main/pull/812
Will work on the config over the weekend to hopefully prevent it from getting stuck again
Acan we remove image-versions from codeowners?
Jyeah
Jdo it, I'm shuffling around but should be around here in a bit to help out with stuff
Apring it
Jyou'll want that in bazzite-dx and -gdx too
AJJdid I do this right?
Ayes. Last file mention has the reviwers
Aso in this case none
Jneat, til
Jcoreos testing is on f42 with 6.14.0
Ja bold move cotton
JI bet we'll get it this week then in stable
Ioh you mean a friday release 
Jhaha yeah
Idamn that is bold
Jstable is usually on tuesdays
Iyep
Jso I'm guessing stable-dailies will start on tuesday
Jwe usually push stable the same day
Jthough I am wondering if we should just leave dailies going and let stable refresh on the usual schedule
Jgive us a few days of extra testing?
Agonna do 6.14 almost before bazzite
Jbut then that's confusing for release notes, etc.
Iyou mean moving stable-daily to f42 now and stable on tuesday?
Jno, stable-daily will automatically go f42 the next build after they push
Jbut we also usually push stable the same time so everyone goes F42 at the same time
Iaah sorry misread
Jbut if we do nothing stable-daily goes on tuesday, and stable goes saturday night
Jthough if they punt a week and we get one more week of ISO work then so much the better IMO
MI think they might break due to the 6.14.0 that's a rawhide kernel
MIf they put a rawhide kernel as the first kernel it will be a wtf
Adont do .2
Ado at least .3
Asorry
A.0
A.0 has a usb issue
Jwe can always stick to 6.13.x for one more month
Jthe way neal is doing it for hyperscale is the best, he just goes from the last -1 kernel
Jso like 6.13.8 is what it's on now, he won't switch to 6.14.x until it's basically done.
MI'm just saying we don't cache the rawhide kernel so our builds will fail if they promote it.
Joh I see
Jsurely they won't promote a rawhide kernel
