I’ve been running Bazzite DX for a few months, but I am still confused about how do I properly track what has changed. I don’t see a newsletter, the news tag in this forum gets rarely updated, and the changelog in GitHub is very confusing. Besides, I also would like to know when there is a change in Bluefin or Bazzite that eventually trickled down to Bazzite DX. What is the recommendation?
You can check Releases · ublue-os/bazzite · GitHub
Those changes will also trickle down to -dx
Looks like the updates are exactly the same as Bazzite, I just installed DX yesterday, was Kernel 6.16, just ran the updater and its updating to the new version now.
Well, like I said: the changelog in GitHub is very confusing. It’s just a list of commits, no real explanation why packages changed, what do they do and how do they fit in the grand scheme of things.
Posts like this one from Fedora, or even this one from Bluefin are much more helpful, but I can’t see anything like that for Bazzite.
DX is just a recipe on top of Bazzite, changes to that recipe will appear in the DX repo, but the bulk of changes will just be the same as Bazzite itself.
Sure, but like I said, those are “changes in Git”. I’m looking for why those changes were made, other than commit logs. ![]()
That is the only place changes are made to DX, all other changes come from Bazzite. You can follow the GitHub releases to see everything.
Okay, I understand the project operates in a certain way, which I am just learning, but I just wanted to show one example of why I think good release notes are important.
Since I follow Jorge Castro on Mastodon, I decided to just go and read his notes about the newest Bluefin release. That’s how I learned that the Tailscale systray exists, and I was able to easily activate it in Bazzite DX.
If I didn’t know I had to go dig into some other distro’s release notes, I would never know about that, because Bazzite’s change logs are just a lot of commit messages that don’t explain the changes the way a newsletter or a blog post do.
And I am fine if this is the way this the way the project decides to work, it’s just confusing that this kind of thing (how to find the changes) is not easily mentioned anywhere in the docs.
Yes things are still a little scattered it seems specially as DX and GDX are the newer extensions of Bazzite, I think things will change/evolve quickly, but it does seem 95% of Bazzite changes are the same on DX, but yes, there is a bunch more cool things that are enabled/added to DX that there may not be anything obvious documenting it, most likely someone else will chime in and prove us wrong ![]()
My update went well, its now on Kernel 6.17, KDE is still 6.4 though.