The linux-next 20260630 integration snapshot was released on July 1, 2026, per the official kernel.org linux-next release archive (https://www.kernel.org/pub/linux/kernel/next/). It aggregates vetted, maintainer-approved patches and previews the full set of changes targeted for the upcoming Linux 6.10 kernel merge window.
What Is the Linux-Next 20260630 Snapshot?
The snapshot aggregates patches that have passed initial review across all kernel subsystems. It catches merge conflicts, build failures, and regressions before maintainers submit finalized code to Linus Torvalds for inclusion in the mainline tree.
For kernel developers, hardware vendors, and enterprise sysadmins, it offers the earliest look at confirmed, low-risk changes slated for 6.10. These include updated driver support, filesystem improvements, and security patches.
The linux-next tree is maintained by veteran kernel developer Stephen Rothwell, as outlined in the official linux-next project documentation (https://www.kernel.org/doc/html/latest/process/linux-next.html). It has been published daily via kernel.org since its 2008 launch as the official kernel integration testbed, marking 18 years of continuous operation as of 2026.
Snapshots are built from maintainer-submitted git trees immediately after each stable kernel release, following a standard cadence established over the project’s 18-year operational history. Patches included in the 20260630 snapshot have already passed review and approval from the relevant kernel subsystem maintainer, making them unlikely to be dropped before the 6.10 merge window closes.
Only critical, last-minute regressions typically lead to patch removal at this stage of the release cycle.
The 20260630 release includes all changes that cleared the initial review process for the 6.10 development cycle as of June 30, 2026, per the official kernel.org linux-next release archive (https://www.kernel.org/pub/linux/kernel/next/). It is the final pre-merge-window integration build, meaning patches not included in this snapshot will not be part of the default 6.10 release unless deemed critical after the merge window closes.
The merge window for Linux 6.10 is scheduled to open immediately following the release of the Linux 6.9 stable kernel, per the kernel project’s published development process documentation (https://www.kernel.org/doc/html/latest/process/development-process.html). It typically lasts 2 weeks, after which only bug fix patches are accepted for the 6.10 release candidate cycle.
Who Uses the Linux-Next Snapshot?
For hardware vendors, the snapshot provides an early opportunity to validate new device drivers against the upcoming kernel release. This reduces the risk of compatibility issues when 6.10 launches, as the integration tree catches driver-related regressions before code is merged into the mainline kernel.
For example, a vendor developing a new PCIe 5.0 NVMe driver can test the driver against the 20260630 snapshot to confirm compatibility with upcoming 6.10 storage stack changes before the 2-week merge window closes.
Enterprise Linux distribution maintainers also use linux-next to test upcoming kernel changes against their supported software and hardware stacks. This ensures smooth upgrades for end users when the stable release ships, as distribution teams can identify and work around breaking changes before they reach production systems.
The 20260630 snapshot is available for download via the official kernel.org public release directory (https://www.kernel.org/pub/linux/kernel/next/), accessible via git repository or compressed tarball for offline testing. The snapshot is released under the GNU General Public License v2 (GPLv2), the standard license for all mainline Linux kernel releases.
FAQ: Linux-Next 20260630 and Linux 6.10
When does the Linux 6.10 merge window open?
The merge window opens immediately following the release of the Linux 6.9 stable kernel, per the kernel project’s published development process documentation (https://www.kernel.org/doc/html/latest/process/development-process.html). It typically lasts 2 weeks, after which only bug fix patches are accepted for the 6.10 release candidate cycle.
Who maintains the linux-next integration tree?
Veteran kernel developer Stephen Rothwell has maintained the daily-published linux-next tree since its 2008 launch as the official kernel integration testbed, per the official linux-next project documentation (https://www.kernel.org/doc/html/latest/process/linux-next.html). Snapshots are built from maintainer git trees after each stable kernel release.
What types of changes are included in the 20260630 snapshot?
The snapshot includes all patches that passed maintainer review for the 6.10 cycle as of June 30, 2026, per the official kernel.org linux-next release archive (https://www.kernel.org/pub/linux/kernel/next/). This includes updated device drivers, filesystem improvements, security patches, and core kernel subsystem changes, all aggregated from maintainer-submitted git trees.
Where can I download the 20260630 snapshot?
The snapshot is available via the official kernel.org public release directory (https://www.kernel.org/pub/linux/kernel/next/), accessible via git repository or compressed tarball for offline testing.
Bottom line: Kernel developers and hardware vendor engineering teams should test drivers and kernel modules against the linux-next 20260630 snapshot immediately to catch compatibility issues with upcoming 6.10 changes before the 2-week merge window closes, as this is the final pre-merge-window integration build and patches not included here will not be part of the default 6.10 release unless deemed critical post-merge. Enterprise Linux distribution maintainers should validate workload compatibility with 6.10 security and filesystem updates against the snapshot prior to the merge window opening, while end users should wait for the first 6.10 release candidate for production deployments.
