Hi, as you probably know, the more features we backport, the higher will be the maintenance cost overtime so as a strategy, we need to be very conservative. I sent a mail some days ago about the

Hi, one of the key parts of the maintenance work is to follow the Common Vulnerabilities and Exposures (CVE)[1] and the fixes that comes out of them, in this case, to the kernel. We can check

Hello I work for consumer product and so, I join Japan Technical Jamboree under CEWG since 4 years ago. I feel that this is important topic. I propagate "LTS" to my company since 4 years ago. This

Hi, In the past Members Meeting, last Monday, this idea was discussed. Finally the decision taken was to stick to the (S)LTS term, that is, including the word support, instead of turning it into

Hi, I had an issue with my e-mail client. Apologies for sending the mail twice. -- Agustin Benito Bethencourt Principal Consultant - FOSS at Codethink agustin.benito@...

Hi, Correction: the goal of the white paper is to provide an overview/status of CIP today. -- Agustin Benito Bethencourt Principal Consultant - FOSS at Codethink agustin.benito@...

Hi, I am writing a description for the wiki and this topic came to my mind. It is just a detail... I would like to propose that we say "maintenance" instead of "support" when referring to the

Hi, if you have any update not included in this mail, feel free to add it. I do not intend to provide a full weekly report but to inform about the activity I am aware of. ++ Meetings * Members

Hi, The ELCE 2016 video of the CIP talk has been published: https://www.youtube.com/watch?v=FcL2rc2o8-4&index=123&list=PLbzoR-pLrL6pRFP6SOywVJWdEHlmQE51q I added it to the events page of the wiki:

Interesting to read: https://lwn.net/Articles/705220/ (subscriptions only until next week) In a nutshell: Folks are unhappy with the selection and review process of patches that go into stable

Dear CIP friends, At ELCE Thursday Oct 13th, the CIP group had a f2f meeting. After having lunch together, Board members met for about an hour. After that the rest of the members joined and discussed

Hi, in preparation to start reporting about the testing efforts, I have added some content to the wiki to provide context. Please let me know if there is anything wrong or that might be

Hi, (2016/09/27 17:29), Agustin Benito Bethencourt wrote: We (our company members) agree. We think CIP doesn't need to kepp the kernel API/ABI. Best regards, Hidehiro Kawai Hitachi, Ltd. Research

Hi, (2016/09/22 21:56), Agustin Benito Bethencourt wrote: I agree on that. CIP don't need to care about out-of-tree drivers. I think it is important to prepare for zero-day attacks, and the

Hi, (2016/09/22 18:42), Agustin Benito Bethencourt wrote: Basically, releasing the kernel as source is sufficient. But if we release it as binary only for the specific reference board, users may be

Hi, I'm sorry for the late response. (2016/09/22 18:31), Agustin Benito Bethencourt wrote: Assuming we release new products in every 2 years, 2-3-year release cycle would be feasible. Maintaining

Nit: it's stable_kernel_rules.txt. We should start this way and augment/adjust rules after discussions as we find potential conflicts. Sounds reasonable to me in general. Jan -- Siemens

Ack. Not sure how to read these threads as I didn't manage to follow their evolution: This aspect of support constraints is still in scope? I think it will be important in order to keep backporting

Hi, At LinuxCon EU, during the CIP talk it was announced that the first CIP kernel will be 4.4 Please find the slides of all the 2016 talks about CIP in our wiki[1]. [1]

Hi, the slides[1] from the talk "Long-Term Maintenance, or how to (mis-)manage embedded systems for 10+ years" by Jan Luebbe are available. I assume by next week we will have the video. [1]