Linux: Where Are We Going
summary
Discussion states the kernel is on a rapid merge cadence with roughly 10,000 patches per release from over a thousand contributors, most releases landing on a two to three month cycle; about 60% of changes target drivers so automated testing misses many regressions. The project relies on modular subsystems and stronger maintainer teams, recommends multiple maintainers per tree, warns short cycles spike patch volume, and asks people to test the current git tree before rc1.
AI-written summary · about
chapters (9)
- 0:00Welcome
- 1:15Linux kernel development
- 3:50Kernel development travel
- 7:27Testing open-source projects
- 9:3423 years of kernel decisions
- 13:50Release cycle debate
- 17:53Advice for kernel devs
- 20:42Becoming a maintainer
- 24:15Linux’s future
related talks
44mLinux Weather Forecast
31mLinus Torvalds in Conversation with Dirk Hohndel
41mThe Kernel Report
42mThe Kernel Report
41mChallenges Around Long-Term Kernel Maintenance
34mHow to Decide the Linux Kernel Version
53mAn engineer's guide to Linux Kernel upgrades
01h 06mWhat's up in the land of the Linux kernel