Call for Testing: GNOME 48 for Bluefin LTS (Beta)

Guardians, the CentOS Hyperscale SIG has been cooking and are bringing GNOME 48 to CentOS.

We’ll be testing in a dedicated testing branch so we can bring this to Bluefin LTS. To switch from an existing Bluefin LTS machine (DO NOT REBASE FROM FEDORA-BASED BLUEFINS):

sudo bootc switch ghcr.io/ublue-os/bluefin:lts-testing --enforce-container-sigpolicy

We’ll be revving fast and hard in this branch so we’re looking for people to file issues, there’s some parity ones being filed already: GitHub · Where software is built

No timeline as to when this will merge into main, and no dx or nvidia at this time.

3 Likes

This is very timely! The recent 6.14 kernel has not been smooth for me and was causing lots of freezes. Unfortunately even GTS was hit due to Fedora’s kernel upgrade policy. I was wishing I could have bluefin with an LTS kernel and lo and behold came across this thread. Avidly waiting for the first stable release.

I am sure there are a lot of people like me who have well supported hardware that just want a reliable stable foundation and kernel that does not cause any disruption. At the same time, an up to date DE and software will let us benefit from new features that actually improve our experience.

Just to be clear it’s a hyperscale kernel, 6.14.6 as of now. We originally were on the LTS 6.12 kernel but that’s not really a long term viable desktop kernel.

EDIT: Introduction to Bluefin LTS | Bluefin has more info!

Ah, interesting.

The kernel version is surprising. In fact, it seems to be ahead of GTS as fedora coreOS is currently at 6.14.5!

I would have expected a release cadence more similar to Ubuntu LTS HWE kernel.

p.s. the faulty kernel was 6.14.3. Some user reports in the wild:

If the Centos hyperscale update policy would have upgraded to this kernel then this LTS still seems a bit too cutting edge!

Yeah the kernel cadence is what I want to check out. In this case, I do know that some framework hardware is making its way to that team. :smiley:

The beta will shake that down and that real world testing is really valuable, so the goal for us using this is to provide feedback. It’s been a great kernel for me since there were some regressions for amd users and we pinned them in Aurora and Bluefin. So I am interested in seeing how this approach works in practice!

1 Like

Great! Looking forward to seeing the iterations on this.

While I am not a fan of snaps, the vision of Ubuntu Core Desktop (still not realized 2 years later!) is very appealing.

It also introduces the concept of modularity to the user experience, where users may experiment with alternative desktop environment snaps while remaining on a highly stable, signed and secure LTS base.

https://ubuntu.com/blog/ubuntu-core-an-immutable-linux-desktop

Hoping Bluefin LTS makes that a reality :slightly_smiling_face:

Is the vision to update GNOME every six months like the other Bluefin streams? That doesn’t feel very LTS to me, although that’s very much a knee-jerk reaction after many years of Ubuntu-style LTS. I’ve seen a fair amount of drama related to big disruptive GNOME changes that seems to get settled by the time the LTS or EL ecosystem update rolls around. I might have a different opinion after a few more cycles on the GTS 6-month plan.

I get there’s a need to update the DE (even Red Hat did it IIRC for RHEL 6 or 7). But I’m not sure what the right cadence should be given the somewhat longer CentOS lifecycle and potential LTS use cases (non-tech user who hates change, work laptop/VM/VDI, or trauma response to a rough update cycle).

The team has decided to not pursue a Bluefin LTS.

It won’t be going out of beta. The repository is up for adoption if you want to adopt it. We will continue to publish builds for a while (since it’s basically automated it doesn’t cost us anything), but I recommend moving off of it over the course of the summer.

Thanks to all of you who helped participate in testing!