User Tools

Site Tools


civilinfrastructureplatform:cipkernelmaintenance

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
civilinfrastructureplatform:cipkernelmaintenance [2017/02/21 14:03]
bwhct Update link to stable kernel rules (now in reST format)
civilinfrastructureplatform:cipkernelmaintenance [2017/11/09 17:20]
anniefisher
Line 1: Line 1:
 ====== Kernel Maintenance ====== ====== Kernel Maintenance ======
  
-CIP announced ​two relevant decisions during ​the second half of 2016: +At the 2017 Embedded Linux Conference Europe, the CIP Project ​announced the new CIP Core. The CIP Core project aims to provide minimal reference file system images and SDK’s to test and demonstrate the use of the CIP kernel and the CIP Core packages, ​selected set of open source software components that require super long-term support. 
-   * At LinuxCon North America 2016 we announced Ben Hutchings as the CIP kernel ​maintainer. Ben is currently the Debian Long Term Support kernel maintainer ​and a reputed kernel hackerspecialised in kernel maintainership+ 
-   * At Embedded Linux Conference Europe 2016 we announced that our first Super Long Term Support kernel branch will be based on Linux 4.4.+Within the open source base layerthe CIP Core connects the CIP Kernel with non-CIP packages
 + 
 +The implementation of the CIP Core is based on the Deby distribution,​ a reproducible and maintainable embedded ​Linux distribution based on pokyDeby overlays meta-debian on top of poky to build file system images out of Debian long-term supported source code packages. The associated source code (metadata) is available on the CIP Core repository and this first release contains support for the following CIP reference hardware: 
 + 
 +iWave RZ/G1M Qseven Development Kit 
 + 
 +Beaglebone Black 
 + 
 +QEMU x86_64 
 + 
 +DE0-Nano-SoC development kit. 
 + 
 +Users of CIP Core can easily extend or customize the reference file system by adding some of the packages already supported by Deby (non-CIP packages). 
 + 
 +For more about CIP Core, visit the wiki page [[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​cip-core]] , follow the quickstart [[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​cip-core-quickstart]]or check out the source code. You can also register in the CIP’s public mailing list to learn more about CIP’s technical roadmap and participate in discussions.
  
 ===== Maintenance policies ===== ===== Maintenance policies =====
Line 57: Line 71:
 Once we have [[civilinfrastructureplatform:​ciptesting|automated testing]] in place, a release candidate must be tested on all the platforms that are covered, with no regressions,​ before it is tagged as a release. Once we have [[civilinfrastructureplatform:​ciptesting|automated testing]] in place, a release candidate must be tested on all the platforms that are covered, with no regressions,​ before it is tagged as a release.
  
-As we will be backporting fixes from mainline, which may change in-kernel APIs, we will not guarantee API or ABI stability within an SLTS branch. ​ It is the responsibility of members to update any out-of-tree components they use in case they are affected by such a change. ​ However, incompatible changes to user-space APIs or ABIs will not be acceptable.+As we will be backporting fixes from mainline, which [[https://​git.kernel.org/​cgit/​linux/​kernel/​git/​torvalds/​linux.git/​tree/​Documentation/​process/​stable-api-nonsense.rst|may change in-kernel APIs]], we will not guarantee API or ABI stability within an SLTS branch. ​ It is the responsibility of members to update any out-of-tree components they use in case they are affected by such a change. ​ However, incompatible changes to user-space APIs or ABIs will not be acceptable.
  
 ===== Support ===== ===== Support =====
Line 74: Line 88:
  
 We plan to track [[https://​cve.mitre.org/​about/​|CVE]] status in each branch and provide this information either to members or publicly. We plan to track [[https://​cve.mitre.org/​about/​|CVE]] status in each branch and provide this information either to members or publicly.
 +
 +[[start|Back to the parent page]]
  
civilinfrastructureplatform/cipkernelmaintenance.txt · Last modified: 2024/05/07 09:18 by nobuhiro.iwamatsu