Linux kernel release process

E195196

The Linux kernel release process is the structured workflow and schedule by which new versions of the Linux kernel are developed, tested, stabilized, and officially published to users and distributions.

All labels observed (2)

How this entity was disambiguated

Statements (51)

Predicate Object
instanceOf software development workflow
software release process
afterMergeWindow first release candidate (rc1)
aimsTo provide a stable and reliable kernel for users and distributions
appliesTo Linux kernel
documentedIn Documentation/process/ in the Linux kernel source tree
Linux kernel MAINTAINERS file
Linux kernel development process documentation on kernel.org
finalReleaseCriteria sufficient stabilization and low rate of serious bug reports
finalReleasePublishedOn kernel.org
finalReleaseTaggedBy Linus Torvalds in the mainline git tree
governedBy Linus Torvalds’ release decisions
includesPhase final release
long-term support maintenance
merge window
release candidate phase
stabilization phase
involvesRole distribution maintainers
stable maintainers
subsystem maintainers
testers and users
ltsSelectionBy kernel.org LTS maintainers and community
ltsTypicalSupportLength at least 2 years
often 6 years or more for some LTS versions
maintainedBy Linux kernel maintainers
mergeWindowControlledBy Linus Torvalds
mergeWindowInput pull requests from subsystem maintainers
mergeWindowPurpose integration of new features and major changes
overseenBy Linus Torvalds
produces long-term support (LTS) kernel releases
mainline kernel releases
release candidates tagged as -rc1, -rc2, etc.
stable kernel releases
qualityAssuranceMechanism automated regression testing
bisecting regressions using git bisect
code review on mailing lists
releaseCandidatePurpose testing and bug fixing
reliesOn wider community testing of release candidates
stableBranchMaintainedBy stable maintainers such as Greg Kroah-Hartman
stableReleaseInput bug fixes backported from mainline
stableReleaseNaming same version number with additional patchlevel increments
startsWith opening of the merge window after a final release
typicalMergeWindowLength approximately 2 weeks
typicalReleaseCandidateCycleLength approximately 6 to 8 weeks
typicalReleaseFrequency roughly every 9 to 10 weeks
usesInfrastructure automated build and test systems
git version control
kernel.org
surface form: kernel.org repositories

mailing lists such as [email protected]
usesVersioningScheme odd minor numbers no longer indicate development-only releases
semantic-like versioning with major.minor.patch numbers

How these facts were elicited

Referenced by (2)

Full triples — surface form annotated when it differs from this entity's canonical label.

Greg Kroah-Hartman influences Linux kernel release process
Linux kernel stable releases follows Linux kernel release process
this entity surface form: Linux kernel mainline releases