civilinfrastructureplatform:cipkernelmaintenance
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
civilinfrastructureplatform:cipkernelmaintenance [2023/07/27 11:58] nobuhiro.iwamatsu [Security fixes] |
civilinfrastructureplatform:cipkernelmaintenance [2024/05/07 08:55] nobuhiro.iwamatsu [Kernel maintenance team] |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| Nobuhiro Iwamatsu, from Toshiba Corporation. and Pavel Machek, from DENX Software Engineering GmbH are the current CIP kernel maintainer. More developers will join in future. | Nobuhiro Iwamatsu, from Toshiba Corporation. and Pavel Machek, from DENX Software Engineering GmbH are the current CIP kernel maintainer. More developers will join in future. | ||
| And when we release the CIP kernel, we will sign it with GnuPG by the maintainers. Each public key can be obtained from the following. | And when we release the CIP kernel, we will sign it with GnuPG by the maintainers. Each public key can be obtained from the following. | ||
| - | * Nobuhiro Iwamatsu ([[http://keys.gnupg.net/pks/lookup?op=get&search=0x32247FBB40AD1FA6|0x5E629EE5232197357B84CF4332247FBB40AD1FA6]]) | + | * Nobuhiro Iwamatsu ([[https://keys.openpgp.org/search?q=5E629EE5232197357B84CF4332247FBB40AD1FA6]]) |
| * Pavel Machek ([[http://keys.gnupg.net/pks/lookup?op=get&search=0x30E7F06A95DBFAF2|0x4F7CF3BBAF478086 4D35D2FD30E7F06A95DBFAF2]]) | * Pavel Machek ([[http://keys.gnupg.net/pks/lookup?op=get&search=0x30E7F06A95DBFAF2|0x4F7CF3BBAF478086 4D35D2FD30E7F06A95DBFAF2]]) | ||
| Line 26: | Line 26: | ||
| === How long will SLTS branches be maintained? === | === How long will SLTS branches be maintained? === | ||
| - | The use cases CIP project is targeting have a life cycle of between 25 and 50 years. In theory, this is the time in which products shipped with the CIP kernel will be under maintenance. However, identifying and backporting relevant fixes becomes increasingly difficult as upstream kernel development diverges further from a stable branch. Any given SLTS branch is unlikely to be maintainable for more than 10-20 years. | + | The use cases CIP project is targeting have a life cycle of between 25 and 50 years. In theory, this is the time in which products shipped with the CIP kernel will be under maintenance. However, identifying and backporting relevant fixes becomes increasingly difficult as upstream kernel development diverges further from a stable branch. Any given SLTS branch is unlikely to be economically maintainable for much more than 10 years. |
| The Linux kernel 4.4 was [[http://lkml.iu.edu/hypermail/linux/kernel/1601.1/01592.html|released on January 10th 2016]]. It was [[https://kernel.org/releases.html|declared LTS (Long Term Support) by the stable team]] which means Greg Kroah-Hartman was supposed to maintain it for two years (Feb 2018) following the kernel LTS process. In September 2017 it was announced that the 4.4 LTS branch will be maintained during 6 years. Another stable maintainer could extend LTS maintenance for some time beyond that. After that period, CIP will maintain it. | The Linux kernel 4.4 was [[http://lkml.iu.edu/hypermail/linux/kernel/1601.1/01592.html|released on January 10th 2016]]. It was [[https://kernel.org/releases.html|declared LTS (Long Term Support) by the stable team]] which means Greg Kroah-Hartman was supposed to maintain it for two years (Feb 2018) following the kernel LTS process. In September 2017 it was announced that the 4.4 LTS branch will be maintained during 6 years. Another stable maintainer could extend LTS maintenance for some time beyond that. After that period, CIP will maintain it. | ||
civilinfrastructureplatform/cipkernelmaintenance.txt ยท Last modified: 2024/05/07 09:18 by nobuhiro.iwamatsu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
