Fedora 44 : testing Django 6.0.4 .

Today I used Fedora 44 beta 12 server on VirtualBox, and I wanted to test how Python works with Django on this Linux distribution. In the Fedora distribution, I have Python version 3.14.3 and Django version 6.0.4. I created a basic project with multiple pages, CSS, JavaScript, and an admin interface. It seems that Django is functional, and the result is very good for a basic project.:

Fedora 44 : Fedora 44 Server with budgie ...

The old laptop on which I was running Fedora broke down. That didn't stop me from testing Fedora Server version 44 beta 12 with the Budgie environment in VirtualBox, and I also made a beginner tutorial video that I share on my YouTube channel - Catalin George Festila.

See this video:

News : Fedora Budgie Spin intro

Today, I saw this good environment and will test with Fedora server on virtualbox because I don't have hardware to test it.

You can see more about this with the Fedora Spin.

The Fedora Budgie Spin showcases the Budgie Desktop, a feature-rich, modern desktop designed to keep out the way of the user. Budgie Desktop uses common desktop design metaphors while offering users sophisticated functionality such as its Raven widget and notification center, and an approachable method to personalization.

Fedora 38: First official release of Fedora Budgie Spin was on 2023.

Fedora 39–44: Continuous updates, better Wayland support, and alignment with upstream Budgie.

Fedora 44 Beta: Ships with Budgie 10.10 and improved integration.

The basic commands for install this fedora package with gdm.

$sudo dnf5 install @budgie-desktop-environment
$sudo dnf5 install budgie-desktop
$sudo dnf5 install @base-x gdm
$sudo systemctl set-default graphical.target
$sudo systemctl enable gdm --now
$sudo reboot

NOTE: If these commands not work then you need to make one update with all packages.

News : the new Linux 7.0 kernel series.

Good news for linux users, see the official website:

From Linus Torvalds Date Sun, 22 Feb 2026 14:40:09 -0800 Subject Linux 7.0-rc1 You all know the drill by now: two weeks have passed, and the kernel merge window is closed. We have a new major number purely because I'm easily confused and not good with big numbers. We haven't done releases based on features (or on "stable vs unstable") for a long long time now. So that new major number does *not* mean that we have some big new exciting feature, or that we're somehow leaving old interfaces behind. It's the usual "solid progress" marker, nothing more. With our normal release schedule of 5-6 releases per year and my antipathy to big version numbers, you should basically expect us to bump the major number roughly every 3.5 years. And yeah, I don't have a solid plan for when the major number itself gets big. But doing the math - by that time, I expect that we'll have somebody more competent in charge who isn't afraid of numbers past the teens. So I'm not going to worry about it. Anyway - despit eany lingering ".0 release" worries that people might have due to experiences with other projects, this was one of those fairly smooth merge window for me. I define those as the merge windows where I don't have to bisect boot failures on any of my machines. Admittedly this time around that was because I caught one failure case early before I *actually* booted into it, but hey, that still technically counts as "smooth" to me. But your milage may vary. Which is why you should now all drop everything, run to your computers, and test-build and test-boot a shiny new kernel. The fact that it all works for *me* is good, but let's make sure it works for others too, ok? Just kidding. A leisurely stroll after you've finished chewing is fine. ...