Differences

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

--- civilinfrastructureplatform:cipkernelmaintenance [2017/11/17 19:48]
anniefisher
+++ civilinfrastructureplatform:cipkernelmaintenance [2017/12/07 14:24]
Agustin Benito Bethencourt erased the release article
@@ Line 1: / Line 1: @@
 ====== Kernel Maintenance ======
-October 23, 2017 – The Civil Infrastructure Platform (CIP), which aims to provide a base layer of industrial grade open source software components, tools and methods to enable long-term management of critical systems, today announced the release of the CIP Core. The CIP Core, a reference minimal file system that offers a customizable environment that developers can use to test the CIP kernel and core packages, was on display at Embedded Linux Conference Europe with planned workshops, demos and Q&A sessions.
+This wiki page describes the policies and recommendations that the CIP kernel maintainers are following in order to maintain the CIP kernel beyond the current periods established by the enterprise industry, in order to meet Industrial Grade requirements.
-CIP aims to speed implementation of Linux-based civil infrastructure systems, build upon existing open source foundations and expertise, establish de facto standards by providing a base layer reference implementation, and contribute to and influence upstream projects regarding industrial needs.
+===== Kernel maintenance team =====
-Hosted by The Linux Foundation, CIP addresses the needs of long-term software for the power generation and distribution, water, oil and gas, transportation and building automation industries. CIP members such as Codethink, Hitachi, Plat’Home, Renesas, Siemens and Toshiba are working to create a reliable and secure Linux-based embedded software platform that can be sustained more than 10 years and up to 60 years.
+Ben Hutchings, from Codethink Ltd. is the initial CIP kernel maintainer. Daniel Wagner, from Siemens AG, joined in 2017 the kernel maintenance team as -rt branch of the CIP kernel maintainer. More developers will join in the coming future.
-“CIP is committed to creating, testing and maintaining an open source software foundation needed to deliver essential services for civil infrastructure and economic development on a global scale,” said Yoshitake Kobayashi, Chair of CIP’s Technical Steering Committee and the Senior Manager of Open Source Technology Department at Toshiba. “The CIP Core is a major milestone that will provide a platform for developers to easily build a reference file system and quickly test the CIP kernel with specific application and use cases. This customizable testing will eventually became a part of the product solution.”
+===== CIP kernel maintenance policies =====
-CIP Core features include:
-- Creating reference file system images to test and demonstrate use of the CIP kernel and core packages, a selected set of open source software components that require super long-term support.
-- Achieving its first milestone after releasing reference file system images for the Beaglebone Black, the iWave RZ/G1M Qseven Development Kit, QEMU x86_64 and the DE0-Nano-SoC development kit.
-- Consolidating the CIP kernel and core packages into a minimal reference file system that can be tested and used for further development.
-- Leveraging released file system images that were generated with Deby, a reproducible and maintainable embedded Linux distribution currently based on poky and Debian LTS source code.
-Board at Desk v1.0:
-CIP also recently launched Board AT Desk (B@D) v1.0, a customized and easy to deploy instance of the kernelci and LAVA projects that should allow developers to test Linux kernels on boards connected to their own development machines using the tooling provided by one of the most successful Open Source testing projects, kernelci.org. B@D v1.0 is provided as a vagrant virtual machine (VM) image/recipe and as a VM image, known as a Vagrant box.
-With this release, CIP is moving towards a “shared and trusted testing” target for not just those directly involved in maintaining the CIP kernel but any kernel developer that has physical access to a board. It reduces the deployment, configuration and maintenance costs. B@D introduces a “local” approach to kernelci.org which is a distributed service centrally managed. In addition, CIP intends to increase the number of developers and organizations willing to participate in kernelci.org by providing a simple mechanism to evaluate the technologies developed by that community (LAVA and kernelci) which CIP considers upstream. For more information about the B@D v1.0, read this blog post [[https://www.cip-project.org/blog/2017/10/18/cip-launches-bd-v1-0]].
-===== Maintenance policies =====
 ==== CIP kernel - SLTS kernel ====
@@ Line 26: / Line 13: @@
 **When does CIP define/label a kernel as SLTS (Super Long Term Support)?**
-New major versions of commercial Linux distributions are released at 3-4 year intervals, so that typically only 4 versions need to be supported at one time.  Given that CIP's support period is meant to be even longer, it won’t be sustainable to extend every LTS branch, but only to take on a new branch every 2-4 years.
+New major versions of commercial Linux distributions are released at 3-4 year intervals and maintained over a  10'13 years, so that typically only 3-4 versions need to be supported at one time.  Given that CIP's support period is meant to be even longer, it won’t be sustainable to extend every LTS branch, but only to take on a new branch every 2-4 years.
 The longer the intervals between new SLTS branches, the greater need there will be for CIP or individual members to backport new hardware support (which carries its own risks). This trade-off is perhaps the most difficult issue to decide.
@@ Line 36: / Line 23: @@
 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 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 will maintain it for two years (Feb 2018) following the kernel LTS process. 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.
-November 17, 2018 Update:  Linux version 4.4.98-cip13 was released by Ben Hutchinson.  This removes the in-tree firmware, adds support for some new hardware watchdog features, and includes all the fixes from stable versions 4.4.93-4.4.98 inclusive.
 ==== Suitable changes ====
@@ Line 64: / Line 49: @@
   * Some features, particularly those labelled as experimental, may also be excluded from support.  We have not done so yet.
-Unlike an LTS branch, an SLTS branch may include larger changes to
+Unlike an LTS branch, an SLTS branch may include larger changes to support new hardware, to bridge the gap between SLTS branches. However, this should only be done on the newest SLTS branch.
-support new hardware, to bridge the gap between SLTS branches.
-However, this should only be done on the newest SLTS branch.
 ==== Releases ====
@@ Line 76: / Line 59: @@
 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 =====
+Initially, CIP will release a new CIP minor kernel version every couple of months approximately. You can find the [[https://gitlab.com/cip-project/linux-cip|latest CIP kernel]] version in gitlab.
+===== Maintenance =====
 ==== Scope ====
-CIP maintainers will support and respond to bug reports from CIP members and their developers, but not system administrators or end users.
+CIP maintainers will maintain and respond to bug reports from CIP members and their developers, but not system administrators or end users in general, about upstream patches. Bugs should be reported upstream.
+The embedded systems that CIP will be used in will also often require out-of-tree drivers and will sometimes include other changes of unknown quality to their kernel. These modifications are in general unsupported. If a bug is found in such a modified kernel, Members will first demonstrate that it exists in the CIP source release in order for the CIP maintainers to act on it.
-The embedded systems that CIP will be used in will also often require out-of-tree drivers and will sometimes include other changes of unknown quality to their kernel.  These modifications are in general unsupported. If a bug is found in such a modified kernel, Members will first demonstrate that it exists in the CIP source release in order for the CIP maintainers to act on it.
+For specific CIP applied patches, the default communication channel will be the [[https://lists.cip-project.org/mailman/listinfo/cip-dev|CIP-dev]] mailing list.
 ==== Security fixes ====

Wiki

User Tools

Site Tools

Differences

Page Tools