* projected EOL v4.4 SLTS
@ 2023-09-22 14:10 Kadel, Michael
2023-09-26 13:53 ` Jan Kiszka
0 siblings, 1 reply; 6+ messages in thread
From: Kadel, Michael @ 2023-09-22 14:10 UTC (permalink / raw)
To: cip-dev@lists.cip-project.org
[-- Attachment #1.1: Type: text/plain, Size: 1881 bytes --]
Hello cip-dev group,
I do have a question regarding the projected EOL v4.4 SLST.
It is said that the projected EOL v4.4 SLTS is 2027, possibly 2036.
When can we expect a decision that the v4.4 SLTS is extended to 2036 or not?
Thanks a lot,
Michael
Mit freundlichen Grüßen / Best Regards
KARL STORZ SE & Co. KG
i.A. Michael Kadel
Product Security Analyst
Global Research and Development
Tel.:
E-Mail: Michael.Kadel@KarlStorz.com<mailto:Michael.Kadel@KarlStorz.com>
Follow KARL STORZ: [cid:image001.jpg@01D9ED6F.572BA090] <https://www.linkedin.com/company/karlstorz/> [cid:image002.jpg@01D9ED6F.572BA090] <https://www.facebook.com/KARLSTORZ> [cid:image003.gif@01D9ED6F.572BA090] <https://www.youtube.com/channel/UCLd331YH_xb-YcssLVdcvEQ>
www.karlstorz.com<http://www.karlstorz.com/>
Hausadresse:
KARL STORZ SE & Co. KG
Betriebsstätte Berlin
Scharnhorststraße 3
10115 Berlin/Germany
===========================================================
KARL STORZ SE & Co. KG
Dr.-Karl-Storz-Straße 34
78532 Tuttlingen/Germany
Sitz der Gesellschaft/ Place of Business: Tuttlingen
Handelsregister/ Commercial Register: Stuttgart HRA 450442
USt.-ID-Nr./ VAT-ID-No.: DE 142931059
WEEE-Reg.-Nr./ WEEE Reg.-No.: DE 74465858
Persönlich haftender Gesellschafter/ Unlimited Partner:
KARL STORZ Verwaltungs SE
Dr.-Karl-Storz-Straße 34
78532 Tuttlingen/Germany
Sitz der Gesellschaft/ Place of Business: Tuttlingen
Handelsregister/ Commercial Register: Stuttgart HRB 762524
Geschäftsführender Direktor/ Managing Director:
Karl-Christian Storz
Vorsitzende des Verwaltungsrats/ Chair of the Supervisory Board:
Dr. h. c. mult. Sybill Storz
===========================================================
Datenschutzmitteilung für Geschäftspartner / Business Partner Data Protection Notice<https://www.karlstorz.com/business-partner-data-protection.htm>
[-- Attachment #1.2: Type: text/html, Size: 14003 bytes --]
[-- Attachment #2: image001.jpg --]
[-- Type: image/jpeg, Size: 728 bytes --]
[-- Attachment #3: image002.jpg --]
[-- Type: image/jpeg, Size: 702 bytes --]
[-- Attachment #4: image003.gif --]
[-- Type: image/gif, Size: 699 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: projected EOL v4.4 SLTS
2023-09-22 14:10 projected EOL v4.4 SLTS Kadel, Michael
@ 2023-09-26 13:53 ` Jan Kiszka
2023-09-27 7:28 ` Kadel, Michael
0 siblings, 1 reply; 6+ messages in thread
From: Jan Kiszka @ 2023-09-26 13:53 UTC (permalink / raw)
To: Kadel, Michael, cip-dev@lists.cip-project.org
On 22.09.23 16:10, Kadel, Michael wrote:
> Hello cip-dev group,
>
> I do have a question regarding the projected EOL v4.4 SLST.
>
> It is said that the projected EOL v4.4 SLTS is 2027, */possibly 2036./*
Where exactly was it stated that we may do 20 years kernel support? Or
current maintenance commitment is documented here:
https://wiki.linuxfoundation.org/civilinfrastructureplatform/start#kernel_maintainership
> When can we expect a decision that the v4.4 SLTS is extended to 2036 or not?
>
So far, no one asked us to do such a long support. Are you aware of such
use cases and tell us more about them?
But also note that CIP as project and with its current contributor base
is not growing at a pace that would allow us to extend the kernel
support that long. CIP is not for free, and can only use this chance to
remind our users to contribute to it to ensure that we can continue to
achieve our goals.
Jan
--
Siemens AG, Technology
Linux Expert Center
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: projected EOL v4.4 SLTS
2023-09-26 13:53 ` Jan Kiszka
@ 2023-09-27 7:28 ` Kadel, Michael
2023-09-28 6:52 ` Jan Kiszka
0 siblings, 1 reply; 6+ messages in thread
From: Kadel, Michael @ 2023-09-27 7:28 UTC (permalink / raw)
To: cip-dev
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Hi Jan,
thanks for your fast answer.
I found this vague statement ".. *possibly 2036* " under: Linux kernel version history - Wikipedia ( https://en.wikipedia.org/wiki/Linux_kernel_version_history )
A use case:
End of Service for medical devices can vary from 5 to 10 years.
If the End of Life of a medical device was announced in 2018 or later, it runs out of support (e.g. cyber security patches for linux kernel v4.4)
This then leads to expensive alternative measures.
Again, thanks for clarification,
Michael
[-- Attachment #2: Type: text/html, Size: 615 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: projected EOL v4.4 SLTS
2023-09-27 7:28 ` Kadel, Michael
@ 2023-09-28 6:52 ` Jan Kiszka
2023-10-02 11:59 ` Kadel, Michael
0 siblings, 1 reply; 6+ messages in thread
From: Jan Kiszka @ 2023-09-28 6:52 UTC (permalink / raw)
To: Kadel, Michael, cip-dev
On 27.09.23 09:28, Kadel, Michael wrote:
> Hi Jan,
>
> thanks for your fast answer.
>
> I found this vague statement "..*/possibly 2036/*" under: Linux kernel
> version history - Wikipedia
> <https://en.wikipedia.org/wiki/Linux_kernel_version_history>
>
Oh, thanks for the pointer! Both this as well as the original source
have been fixed now.
> A use case:
> End of Service for medical devices can vary from 5 to 10 years.
> If the End of Life of a medical device was announced in 2018 or later,
> it runs out of support (e.g. cyber security patches for linux kernel v4.4)
> This then leads to expensive alternative measures.
Good to know. But that also underlines that we are with about 10 years
in the sweet spot of the demand.
Jan
--
Siemens AG, Technology
Linux Expert Center
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: projected EOL v4.4 SLTS
2023-09-28 6:52 ` Jan Kiszka
@ 2023-10-02 11:59 ` Kadel, Michael
2023-10-03 20:26 ` Jan Kiszka
0 siblings, 1 reply; 6+ messages in thread
From: Kadel, Michael @ 2023-10-02 11:59 UTC (permalink / raw)
To: cip-dev
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
Hi Jan,
what is necessary in terms of resources and budget for us as a company
to extend the Linux Kernel v4.4 i.e. for further 5 years (EOL 2032)?
More precise, how many FTEs should work on this kernel extension
and is it also possible to purchase such a service by the CIP?
Michael
[-- Attachment #2: Type: text/html, Size: 340 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: projected EOL v4.4 SLTS
2023-10-02 11:59 ` Kadel, Michael
@ 2023-10-03 20:26 ` Jan Kiszka
0 siblings, 0 replies; 6+ messages in thread
From: Jan Kiszka @ 2023-10-03 20:26 UTC (permalink / raw)
To: Kadel, Michael, cip-dev
On 02.10.23 13:59, Kadel, Michael wrote:
> Hi Jan,
>
> what is necessary in terms of resources and budget for us as a company
> to extend the Linux Kernel v4.4 i.e. for further 5 years (EOL 2032)?
> More precise, how many FTEs should work on this kernel extension
> and is it also possible to purchase such a service by the CIP?
CIP is not a service provider but rather a project that aims at sharing
common costs of the members. However, the CIP project is in discussions
with a potential partner who could offer individual services on top.
If that could include extra 5 years would be to on different page - the
longer the support is, the less experience there is about the efforts
for backporting.
Jan
--
Siemens AG, Technology
Linux Expert Center
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-10-03 20:26 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-09-22 14:10 projected EOL v4.4 SLTS Kadel, Michael
2023-09-26 13:53 ` Jan Kiszka
2023-09-27 7:28 ` Kadel, Michael
2023-09-28 6:52 ` Jan Kiszka
2023-10-02 11:59 ` Kadel, Michael
2023-10-03 20:26 ` Jan Kiszka
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox