Well, folks, here we are. Linux 7.0-rc1 has landed, and if you were expecting fireworks because of that shiny new major number, you might want to take a breath.
Linus Torvalds officially closed the merge window and tagged 7.0-rc1, but he was quick to tamp down any drama. The jump to 7.0 is not about some sweeping reinvention of the Linux kernel. It is not a “stable vs unstable” reset. It is not a grand redesign. As Linus flatly put it, the new major number exists “purely because I’m easily confused and not good with big numbers.”
Hah! That sure is peak Linus…
He reminded everyone that the project has not done feature-based releases in a “long long time.” A bump to 7.0 does not mean old interfaces are being abandoned. It does not mean something earth-shattering just merged. It is, in his words, the usual “solid progress” marker. Nothing more.
And then he went even further. With the kernel pushing out five or six releases a year, he expects the major version to tick up roughly every three and a half years. As for what happens when those numbers get truly unwieldy, he joked that by then, “we’ll have somebody more competent in charge who isn’t afraid of numbers past the teens.” He is not losing sleep over it.
If you have PTSD from other projects shipping buggy “.0” releases, Linus addressed that too. He described this merge window as “fairly smooth.” His definition of smooth? Not having to bisect boot failures on his own machines. He admitted he caught one failure early before actually booting into it, but, as he said, that still technically counts.
Of course, he still wants people to test it. He half-mockingly told everyone to drop everything and go test-build and test-boot the shiny new kernel, before dialing it back with a joke about taking a leisurely stroll after you finish chewing. Classic mailing list tone.
Under the hood, Linux 7.0-rc1 looks exactly like what seasoned kernel watchers expect. About two-thirds of the changes are driver updates. The remaining third is a mix of architecture work, filesystem changes, tooling, documentation, and core kernel code.
The VFS layer saw a heavy round of updates, including timestamp handling, mount changes, error reporting tweaks, atomic_open work, and continued Rust integration. Btrfs, XFS, ext4, f2fs, NTFS3, and others all got attention. io_uring continues to evolve with new features and fixes. Memory management, slab, block, and scheduler code were also refreshed.
Architectures from x86 and arm64 to RISC-V, MIPS, LoongArch, s390, and even older platforms like m68k and parisc saw updates. Security subsystems including SELinux, AppArmor, Landlock, integrity, and TPM were touched as well. Virtualization stacks like KVM, Xen, Hyper-V, and virtio did not sit this one out either.
In other words, Linux keeps moving. Not with hype. Not with marketing slogans. Just relentless incremental engineering.
For everyday Linux users running a stable distro, this is the beginning of a cycle, not something you install tomorrow. For developers, however, this is where the real work starts. rc1 means test, test, and test again.
Linux 7.0 sounds dramatic. The reality is truly better. It is the same kernel philosophy that has powered everything from Android phones to hyperscale data centers for decades. The number changed. The attitude did not.
