2020 Kernel History Report 082720
2020 Kernel History Report 082720
Summary 3
Introduction 4
Kernel Archeology 5
Conclusion 21
References 23
Impact of Development Process
Best Practices
In 2015, The Linux Foundation’s Core Infrastructure The kernel maintainers meet in person every year
Initiative (CII) program introduced a best practices (except this one) at the Maintainer Summit to discuss
badge for open source projects to publicly determine how to improve their ways of working together. Topics
their software development and security practices10. for the summit are determined by developers raising
The Linux kernel was one of the first projects to get a them on the ksummit-discuss mailing list13. After
badge. As time has evolved, additional practices have a healthy discussion, those that aren’t resolved are
been identified, and these were incorporated into selected to be discussed in person. These meetings are
higher badge levels for projects to strive for11. In June vital to the continuous improvement of the processes
of this year, the Linux kernel joined the small handful that the community follows. Over time there has been
of projects with a gold badge, the top badge level12. a steady growth in the number of contributors and
This is a visible recognition of what’s been there for a commits to the kernel each year. While it is not easy
long time now; the Linux kernel community continues to quantify the impact of these process improvement
to lead on establishing best practices in the areas of meetings, they are likely a positive factor.
software engineering and secure development at scale.
Contributors to the Linux Kernel per Year Commits to the Linux Kernel per Year
In trying to understand the discussions that led to In contrast, today’s v5.8 MAINTAINERS file is now 19,033
the formation of this file, early Linux development lines long and has 150117 maintainers listed18. The v5.8
mailing lists were consulted. Unfortunately, only partial MAINTAINERS file ends with:
records of the discussions are publicly available before
1997, as Linux development took place across multiple THE REST
M: Linus Torvalds <torvalds@linux-foundation.org>
L: linux-kernel@vger.kernel.org
S: Buried alive in reporters
Q: http://patchwork.kernel.org/project/LKML/list/
T: git git://git.kernel.org/pub/scm/linux/
kernel/git/torvalds/linux.git
F: *
F: */
Longterm release kernels start off as a stable kernel There is market pressure for even longer support
with a commitment to maintaining for an extended windows to support some of the applications
period. Distributions like SUSE, Ubuntu, Red Hat, etc. where Linux is being used. For example, the Civil
helped to pioneer this concept, and it was formalized in Infrastructure Platform (CIP) project60 members have a
201058 with the formalization of “longterm” kernels and common interest in having an infrastructure that needs
creation of the stable@kernel.org mailing list. to be maintained for extended periods. The developers
participating in this project have decided to support
Bugs found in the current linux stable kernel are fixed 4.4 and 4.19 as Super Long-term Stable (SLTS) kernel
upstream and then applied to the stable kernel. When release61, 62. It will be interesting to see what tools and
a fix is determined to be applicable to one of the processes these developers create to help make this
longterm release kernels, it is backported and applied. vision possible in the years to come.
Source: https://www.kernel.org/category/releases.html Tools Detect More Fixes for Longterm Linux Kernels