Linux 7.2-rc1 opens the next kernel testing cycle

Linus Torvalds released Linux 7.2-rc1 on June 28, 2026. The first release candidate follows the closure of the two-week merge window, beginning the testing and stabilisation phase for the next kernel.

Torvalds described the cycle as broadly normal. Drivers account for a large share of the changes, while AMD GPU register definitions make up a substantial portion of the patch. The volume of code therefore should not be treated as a count of visible new features.

What rc1 means

Kernel development generally begins with a roughly two-week window for merging major changes. The first candidate marks the transition toward fixing problems and preparing subsequent candidates.

Linux 7.2-rc1 is consequently a development milestone rather than a final Linux 7.2 release. Its arrival also does not establish a guaranteed final launch date: readiness depends on testing and the resolution of outstanding problems.

That distinction helps when reading operating-system news. A change entering a development tree, appearing in a test build and becoming suitable for everyday use represent different stages.

Who should pay attention?

Kernel.org describes RC releases as preliminary versions primarily intended for kernel developers and Linux enthusiasts. Stable and long-term kernels serve different purposes. Distributions may also maintain their own kernels and support arrangements.

For someone who relies on a computer for work or study, the practical questions are where an update comes from and who supports it. A larger version number alone does not establish a reason to change a working environment.

Making testing useful

A tester can contribute more by describing a specific result than by offering a general impression of speed. Did the same device work with the previous kernel? Can the problem be reproduced using the same steps? Recording hardware, version information and reproduction steps makes a report easier for a maintainer to investigate.

This cycle can also provide a useful learning exercise for computing students and programming teams: follow one change, understand its purpose and compare behaviour before and after it. That turns an announcement into a practical lesson in how open-source software matures.

The immediate significance of 7.2-rc1 is the opening of that broader testing process. The final outcome will depend on the work carried out during the following weeks.