Linux Kernel Development Report 25 Anniversary Edition

The Linux Foundation released the 2016 Linux kernel Development Report, which coincided with the 25 anniversary of the Linux kernel (Tengyun technology ty300.com), so it is worth reading more than previous years for more retrospective content.

Linux Kernel Development Report version 2016

Some interesting information:

Since the 3.18 kernel, new features merged from the Linux kernel kernel have been more extensive and new features that involve security are increasing

The introduction of the 4.0 series is only due to the fact that Linus (Basic tutorial Qkxue.net) feels that the minor version number has gone beyond the sum of the number of fingers and toes of the normal person. Every kernel release is a major release in the traditional sense, numbering is no longer important.

The release cycle is more stable for 9 weeks, and the occasional 10 weeks are mainly due to external factors such as Linus vacations or public holidays.

Although the 4.6 version of 13,517 changes quite large, but compared to the 3.5 version of 13722 is still a little bit worse

The kernel 4.9 version will be the next long-term support version following 4.4

As of version 4.7, the Linux kernel contains 21,724,632 lines of code and 54,391 files

The development of version 4.2 has historically been supported by the largest number of commercial companies, with 251 different enterprise contributions for which the code has been submitted

Independent developers do not contribute a lot of code submissions, since the 2.6.11 version, the top 30 independent developers add up to only 16% of the total number of submissions

The number of developers funded by the company accounted for 80% of the total, while the number of independent developers has dropped to 7.7%. The reason for this is that there is a shortage of kernel developers and the ability to find jobs.

Intel introduces the most new recruits for Linux kernel kernel development, up to 205 people

25 years of experience and lessons one: Fast release, short release cycle is important

25 years of experience and lessons two: the scalability of the process requires a distributed hierarchy of development patterns, all by Linus a dead man, a clear division of responsibilities to improve efficiency

25 years of experience and lessons three: tools are important, migrating to BitKeeper disruptive improvements to the way you work, and the migration to Git further increases productivity

25 years of experience and lessons four: the principle of identity is very important. If there is an experienced and respected developer who opposes a change, it will not be merged. This ensures that no changes will be made at the expense of a particular user base.

25 years of lessons learned five: it is important to have no Regression principle. Although the occasional practice is imperfect, it ensures that users are not particularly concerned about kernel upgrades.

Turn from: Diligent study qkxue.net

Linux Kernel Development Report 25 Anniversary Edition