Linux 7.0-rc4 Lands Bigger Than Expected

What Happened

Linux 7.0-rc4 Release Drops on Schedule — But Heavier Than Torvalds Hoped

Linus Torvalds posted the Linux 7.0-rc4 release candidate announcement to the Linux Kernel Mailing List on Sunday, March 15, 2026 at 14:15 PDT. The message opened with an admission that the week started calm — then Thursday arrived. A networking subsystem pull request landed mid-week and significantly pushed up the commit count, with additional patches flooding in on Friday and trickling through the weekend.

The result was another release candidate that Torvalds described as running "bigger than usual" — continuing a pattern that has held across rc2 and rc3 as well. rc1 itself was a fairly normal 11,500 commits (excluding merges), but each subsequent candidate has come in a notch above historical norms for its respective stage in the cycle.

Why It Matters

The Networking Pull: Why One Subsystem Can Move the Whole Needle

The Thursday networking merge that inflated rc4 is worth understanding. The Linux kernel's networking subsystem is one of the largest and most active trees in the entire codebase. A single pull from networking maintainer Jakub Kicinski can include TCP stack refinements, new or updated NIC drivers, protocol bug fixes, and changes to core socket infrastructure — all landing as one large batch.

In the context of Linux 7.0 specifically, the networking pull carries extra weight. Earlier in the 7.0 merge window, AccECN (Accurate Explicit Congestion Notification) was enabled by default — a landmark TCP congestion control change that makes Linux 7.0 the first kernel version to ship AccECN on for all users. Subsequent networking pulls in the rc cycle typically include fixes, tuning, and driver updates that ripple out from decisions made during the merge window.

Background

What Is a Release Candidate? A Plain-English Guide for Newcomers

If you're new to kernel development, the release candidate cycle can feel opaque. Here's how it works: after the two-week merge window closes — where major new features land — Torvalds begins tagging weekly rc builds. These are not feature drops; they are stabilization checkpoints where only bug fixes, regression patches, and documentation updates are accepted.

The cycle typically runs from rc1 through rc7 or rc8, with Torvalds releasing the final kernel once the pace of incoming fixes drops to an acceptable low. rc4 landing at the expected week means the 7.0 cycle is healthy. A kernel that reaches rc8 or beyond usually signals a rougher development cycle with persistent regressions; rc7 is the most common stopping point for a clean release.

Timeline

Linux 7.0 Development Cycle — From Merge Window to Final Release

• 1
  Late Jan 2026

  Linux 6.14 released; Linux 7.0 merge window opens for two weeks of new feature submissions. AccECN default-on, version number jump from 6.19 to 7.0, and major subsystem overhauls all land here.
• 2
  Early Feb 2026

  Linux 7.0-rc1 tagged — merge window closes. First release candidate ships with ~11,500 commits, described as a fairly normal size for rc1 of a new major version.
• 3
  Feb–Mar 2026

  rc2 and rc3 both land above average commit counts. Torvalds notes the pattern but attributes it initially to an extra week carried over from the previous cycle.
• 4
  March 15, 2026

  Linux 7.0-rc4 released. Thursday networking pull drives another above-average candidate. Torvalds publicly revises his explanation — he now suspects developer psychology around the new major number is the real cause.
• 5
  Late Mar – Early Apr 2026

  rc5, rc6, and likely rc7 are expected weekly. Each should show a decreasing patch rate as the kernel stabilizes toward its final tag.
• 6
  Mid-April 2026 (Projected)

  Linux 7.0 final release. The exact date depends on whether rc7 or rc8 is required. Most community estimates point to the third or fourth week of April 2026.

What's New

What's Actually Changed in Linux 7.0 So Far

The headline feature confirmed in the 7.0 merge window is AccECN enabled by default — making Linux 7.0 the first kernel to ship with Accurate Explicit Congestion Notification active for all TCP connections. This matters most in data center environments where multiple flows compete for bandwidth, and signals that Linux's TCP stack is now aligned with modern congestion-aware networking hardware.

The version number itself is the other major story. Linux 6.x ran from kernel 6.0 through 6.14 before Torvalds decided the minor version was climbing too high — he has historically bumped the major number when the minor version approaches 20. The jump to 7.0 is cosmetic in terms of compatibility but carries real-world weight: every downstream tool, distro package, and kernel module version check that hard-codes a major version string will need updating.

Technical Details

Linux 7.0-rc4 Release Candidate Testing — How to Run It Safely on Ubuntu or Fedora

Testing release candidates is the fastest way to help the kernel community catch regressions before they ship to millions of users. The safest method is a dedicated test machine or a VM — never a primary production host.

On Ubuntu, the mainline kernel PPA at kernel.ubuntu.com/mainline hosts pre-built .deb packages for each release candidate — no compilation required. On Fedora, the kernel-vanilla-mainline COPR repository provides equivalent mainline builds. For source builds, clone git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git, check out the v7.0-rc4 tag, and compile with your distro's existing config as a baseline.

Found a regression? Report it to the Linux Kernel Mailing List at linux-kernel@vger.kernel.org with full dmesg output, your hardware configuration, and a bisect result if you can produce one. The kernel team takes rc-stage regression reports seriously and typically responds within 48–72 hours.

Market Impact

When Will Your Distro Ship Linux 7.0? A Realistic Timeline

The final Linux 7.0 tag does not mean immediate availability in mainstream distributions. Distros run their own integration, QA, and packaging cycles after an upstream release lands. Here is what to expect based on historical adoption patterns:

LinuxTeck Take

What rc4's "Bigger Than Usual" Status Actually Tells Us

The inflated commit counts in the Linux 7.0-rc4 release cycle are worth watching but not worrying about. The Linux 7.0-rc4 release cycle has now produced three consecutive above-average candidates. Torvalds himself has been transparent: the diffs are small, spread across dozens of subsystems, and there is no single area generating alarm. The networking pull that pushed rc4 over the line is normal kernel housekeeping amplified by timing — late-week batching happens every cycle.

What's more interesting is Torvalds's revised read on why the cycle is running hot. His initial theory — that an extra week in the previous 6.14 cycle carried excess activity forward — has now been revised. He's landed on developer enthusiasm for a new major number as the more likely explanation. Whether or not that theory is correct, it tells you something about how Torvalds reads kernel community psychology after more than 30 years of managing it.

For sysadmins tracking the Linux 7.0-rc4 release: mid-April 2026 remains the working estimate for Linux 7.0 final. If you're planning server kernel upgrade timelines, that is the date to put in your planning documents. For kernel testers: rc4 is your most productive testing window — stable enough to run real workloads, early enough for fixes to make the final cut.