Keynote: in a Conversation with
summary
Kernel development uses a two‑week merge window two weeks then weekly release candidates, typically seven RCs and a final release (about every 2.5 months), but 4.14 may need an extra RC 8 because LTS pressure sped up submissions; fuzzing and tooling like lockdep and compiler sanitizers are catching many driver and concurrency bugs—fuzzing finds malformed-USB/device edge cases—while maintainer churn and the need for 2–4 person maintainer teams makes onboarding new maintainers hard and suggests mentorship/rotation approaches.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:15Release schedule
- 3:20Role models
- 5:10Experience
- 7:10Trust
- 10:03Maintainership
- 15:45Attitude
- 16:55Community Projects
- 19:24What makes a project successful
- 20:05What makes a good developer
- 21:26If you find developing software miserable
- 22:25Dirks love for C
- 25:47Dirks motivation
- 27:47Prediction question
- 29:22Release date prediction
related talks
24mKeynote: The Kernel Report
36mKeynote: Linus Torvalds in Conversation with Dirk Hohndel
26mKeynote: Linus Torvalds in conversation with Dirk Hohndel
40mKeynote: Linus Torvalds, Creator of Linux & Git, in conversation with Dirk Hohndel, VP
26mKeynote: The Kernel Report
35mKeynote: Linus Torvalds, Creator of Linux & Git, in Conversation with Dirk Hohndel
21mKeynote: Linus Torvalds, Creator of Linux & Git, in conversation with Dirk Hohndel
43mLinus Torvalds in conversation with Dirk Hohndel