How the development process works (Documentation/process/2.Process.rst)¶
Community, L. K. (2024). How the development process works (Documentation/process/2.Process.rst). The Linux Kernel documentation.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Collaborative Maintenance
- Contested patches are argued out on the public lists and, when needed, escalated up the maintainer hierarchy to Linus Torvalds, who integrates the merge windows on a roughly two-month release rhythm
This sourceThe process guide describes mailing-list review, the chain of maintainer trees feeding Linus's merge windows, and a two-to-three-month release cycle; it does not describe contested patches being escalated to Linus.
Supported in partVerified against a saved copy of the source
“Early review. Patches are posted to the relevant mailing list, and developers on that list reply with any comments they may have”
- Contested patches are argued out on the public lists and, when needed, escalated up the maintainer hierarchy to Linus Torvalds, who integrates the merge windows on a roughly two-month release rhythm
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:9ea83ccf7e47 · see in the full table