What Linux 7.3-rc7 is on October 12

What happened

On October 12, 2026, kernel.org lists Linux 7.3-rc7 as the mainline kernel. LWN's item the same day is headlined as the kernel prepatch 7.3-rc7. This page does not quote the announcement mail, because that text is not one of the documents filed here. What is filed is the label on the kernel.org front, the LWN headline, and the kernel project's own description of what a release candidate is for. The page filing those three is Futureweb.

What the process document says a candidate is

The kernel development process document describes the cycle after the merge window as a series of release candidates, each meant for testing, ending in a stable release. A -rc tag is the tip under test. It is not the version a distribution is being asked, by that document, to ship as the finished kernel. A license obligation, which is a different open-source fact, is what a license obligates.

What mainline means on that page

Mainline on kernel.org is the development tip, which on October 12 is the tag 7.3-rc7. LWN's headline calls the same tag a prepatch, which matches the suffix. The process document describes release candidates as the testing builds after the merge window and before the stable tarball. It does not list the drivers or the fixes in this candidate, and this page will not invent them from a mail it did not file. A distribution that ships the rc tag as if it were the finished 7.3 kernel is ahead of both the front page and the process document. Testers can build the tip. Everyone else is waiting for a tarball without the rc suffix. When kernel.org's mainline row changes, this snapshot is over, and the new tag is a new sentence. The process document can survive that change because it describes the cycle, not this Sunday's tip. The announcement mail, if it names regressions, is a source this brief has deliberately left closed. Nothing in the process document asks a distribution to install 7.3-rc7 as the stable kernel. The suffix is the warning. LWN's prepatch headline agrees with the suffix, and kernel.org's mainline label says only that this is the tip. A changelog remains out of scope until the announcement mail is itself a source. kernel.org's front page uses mainline for the current development tip. Listing 7.3-rc7 there means that tag is the tip on the day the page is read. It does not mean every tree has moved, and it does not list the bugs the candidate fixes. The desk is Open Source.

Why it matters on this desk

The dependency is a tag a developer can name without pretending the stable kernel has shipped. People who track mainline can test 7.3-rc7. People who wait for the stable tarball are still waiting. Confusing the two is how a prepatch becomes a fake release note. A version number in a different project is what a version number has to mean.

What this page will not invent

Linus's mail, if it lists regressions or a hoped-for final date, is not reproduced here and not paraphrased from memory. A wire headline that names 7.3-rc7 is not a changelog. This page will not add drivers, filesystems, or fixes the announcement might contain. The software desk, for a browser version dated the same week, is Software.

Where the documents overlap

kernel.org and LWN agree on the tag: 7.3-rc7, in October 2026, as a prepatch rather than a finished release. The process document does not mention this candidate. It supplies the meaning of the suffix. The overlap is the tag. The meaning is the process. The announcement's particulars are outside the file.

What to watch next

A 7.3-rc8 listing, or a 7.3 stable tarball without the rc suffix, would replace this tip. A quote from the announcement, filed with the mail itself, could add the fixes this page refuses to invent. Another site mirroring kernel.org would not. The October 12 mainline line is the snapshot. Testers and packagers are not the same reader, and the tag does not pretend they are.

What would change the record

If kernel.org's mainline row moves, the tag in the first sentence is stale and should say so. If LWN's prepatch item is corrected, the headline citation moves with it. The process document can stay true across both, because it describes the cycle rather than this week. A stable 7.3 release would be a new brief, with the tarball as the document.

What stays a prepatch

What stays specific is a mainline label. On October 12, 2026, kernel.org lists Linux 7.3-rc7 as mainline, and LWN files the same tag as a prepatch. The kernel process document says release candidates are the testing tags between the merge window and the stable release. This page does not claim a list of fixes, a regression count, or a date for the final 7.3 tarball, because those would have to come from the announcement mail, which is not filed here. A reader can test the candidate or wait. The tag does not, by itself, ask a distribution to ship it as stable. That distinction is the whole brief: rc7 is the tip under test, and the stable cut is a later document.