The official Linux kernel project released the weekly linux-next integration tree for June 30, 2026 linux-next releases, kernel.org, adhering to its fixed public release schedule published on the project’s official website. This pre-merge snapshot aggregates all unmerged, pending kernel patches submitted during the 7-day merge window that opened after the most recent mainline kernel merge cycle closed.
The full source tarball for this release is approximately 1.1GB in size. Incremental daily updates are also available via the public kernel.org git repository for developers tracking changes throughout the week.
This edition gives kernel developers, hardware vendor engineering teams, and Linux distribution maintainers a centralized pre-integration view of pending kernel functionality. It lets them identify patch conflicts, regressions, and hardware compatibility issues before code is merged into the stable mainline branch.
The tree is built automatically on kernel.org infrastructure every weekday. A final consolidated snapshot is published every Tuesday for community testing, per the project’s public development documentation kernel.org.
Hardware vendors, Linux distribution developers, and independent kernel contributors regularly use the tree to validate pending changes against a wide range of hardware and software configurations prior to mainline inclusion. For example, a pending patch for a new storage controller driver would be tested across multiple server and desktop hardware platforms in this tree before being submitted for mainline merge.
What is the linux-next integration tree?
The linux-next tree is a core component of the Linux kernel’s public, open development workflow. It is maintained by lead kernel release coordinator Stephen Rothwell and the kernel project’s release team to catch integration issues early in the development cycle.
Unlike official stable kernel releases (such as the 6.x.y maintenance branches), linux-next includes in-progress patches that have not yet been cleared for mainline inclusion. Official stable releases only contain fully reviewed, tested code that has passed formal subsystem maintainer approval.
All pending patches in the tree are organized by kernel subsystem — including drivers, filesystems, networking, and architecture-specific code — for easy review by testers and contributors. This organization lets contributors quickly locate changes relevant to their specific hardware or software use cases without sifting through unrelated patch submissions.
Details of the June 30, 2026 release
The June 30, 2026 linux-next release aggregates all patches submitted during the 7-day merge window that opened immediately after the most recent mainline Linux kernel merge cycle closed linux-next releases, kernel.org. It represents the full set of pending changes that have not yet been formally approved for mainline merge.
This snapshot serves as a comprehensive preview of functionality that may appear in the next stable Linux kernel release, per the kernel project’s public release timeline. Developers can review the full, itemized changelog and complete patch list for the June 30, 2026 tree via the official kernel.org linux-next releases page.
Entries are sorted by subsystem for targeted review of changes relevant to specific hardware or software use cases. Each entry in the changelog notes the patch submitter, affiliated organization, and a summary of the proposed change, per the official release page format linux-next releases, kernel.org.
Download options for the June 30, 2026 tree
Developers can download the full linux-next tree for June 30, 2026 directly from the kernel.org public file repository kernel.org. Two access options are available to suit different development workflows.
The full source tarball, sized at approximately 1.1GB, contains the complete set of pending patches and full kernel source code for full offline testing and validation. It is ideal for developers who want a static, point-in-time snapshot of the tree as of the June 30, 2026 release date linux-next releases, kernel.org.
For developers tracking incremental changes throughout the week, the public kernel.org git repository allows users to pull daily updates without waiting for the next weekly snapshot. This reduces download volumes for ongoing development work and lets testers identify newly introduced issues as soon as they are added to the tree.
Core purpose and testing workflow
The primary purpose of the linux-next tree is to reduce the number of bugs, regressions, and integration conflicts that make it into mainline stable kernel releases. It does this by providing a centralized, public testing ground for pending patches before they are formally merged.
Kernel maintainers, hardware vendors, and distribution developers regularly test linux-next snapshots to identify issues early in the development cycle. Fixes can be implemented with minimal disruption to the broader kernel ecosystem at this stage.
For example, a pending patch for new consumer GPU hardware would be present in linux-next for 1 to 2 weeks of testing before being submitted for mainline merge. This testing window lets driver developers fix boot failures or display glitches before the patch is merged into mainline, reducing the risk of post-merge regressions for end users when the patch is eventually released in a stable kernel version kernel.org.
Frequently Asked Questions
Is the linux-next tree stable for production use?
No, the linux-next tree is explicitly a development snapshot and is not intended for production use. It contains unmerged, unreviewed patches that may include bugs, regressions, or incomplete functionality. The kernel project recommends linux-next only for testing and development purposes, not for deployment on production systems, per its official documentation kernel.org.
How often is the linux-next tree released?
The linux-next tree is released on a fixed weekly cadence, with new snapshots published every Tuesday as part of the Linux kernel’s standard development schedule. Releases are timed to align with the kernel project’s merge window and development cycle for upcoming stable releases, per the kernel.org public release calendar linux-next releases, kernel.org.
Who maintains the linux-next integration tree?
The linux-next tree is maintained by the Linux kernel project’s release team, with day-to-day coordination from lead kernel release coordinator Stephen Rothwell. He oversees the integration and testing of pending patches prior to mainline merge, per kernel project public records kernel.org.
What is the difference between linux-next and mainline kernel releases?
The linux-next tree contains unmerged, in-progress patches that have not yet been approved for mainline inclusion. Mainline stable kernel releases only contain fully reviewed, tested code that has passed the kernel project’s formal merge process.
Code in linux-next may change significantly or be dropped entirely before it is merged into mainline, per the kernel project’s official development workflow documentation kernel.org.
Bottom line
Bottom line: Kernel developers and hardware testers seeking to validate upcoming Linux kernel features and pending patches can download the June 30, 2026 linux-next integration tree for free from kernel.org linux-next releases, kernel.org. It is explicitly not suitable for production deployment due to its unmerged, unreviewed codebase that may contain unresolved bugs or regressions. The 1.1GB full source tarball is ideal for offline testing, while developers tracking weekly changes can use the public git repository for incremental updates without re-downloading the full 1.1GB snapshot each time.
