4.4.302 is going to be last 4.4 release

4.4.302 is going to be last 4.4 release

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]

Hi!

Greg says:

# Message-Id: <20220201180822.148370751@linuxfoundation.org>
# Subject: [PATCH 4.4 00/25] 4.4.302-rc1 review
# ...
# NOTE!  This is the proposed LAST 4.4.y kernel release to happen under
# the rules of the normal stable kernel releases.  After this one, it will
# be marked End-Of-Life as it has been 6 years and you really should know
# better by now and have moved to a newer kernel tree.  After this one, no
# more security fixes will be backported and you will end up with an
# insecure system over time.
# ...
# Responses should be made by Thu, 03 Feb 2022 18:08:10 +0000.
# Anything received after that time might be too late.

(He sometimes releases kernels before the deadline).

We may want to make any announcements now or just after 4.4.302 is
released... so I guess we should start working on suitable wording.

Something like:

CIP project is committed to maintain 4.4.x kernel till January of 2027
[1]. We are maintaining -cip branch [2], that is stable kernel with about
1000 of patches to support our reference hardware [3] and -cip-rt
branch, with is merge of -rt and -cip trees.

If you for some reason need 4.4.x with bug and security fixes, and are
running similar hardware to our reference hardware (x86-64 and armv7),
-cip tree may be good base for that work. Testing of the -cip tree is
welcome, as is joining the CIP project.

[1] https://wiki.linuxfoundation.org/civilinfrastructureplatform/start
[2] https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-cip-rt
[3] https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware

?

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

RE: [cip-dev] 4.4.302 is going to be last 4.4 release

[nobuhiro1.iwamatsu]

Hi Pavel,
> -----Original Message-----
> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of Pavel Machek
> Sent: Wednesday, February 2, 2022 6:33 AM
> To: jan.kiszka@siemens.com; cip-dev@lists.cip-project.org
> Subject: [cip-dev] 4.4.302 is going to be last 4.4 release
> 
> Hi!
> 
> Greg says:
> 
> # Message-Id: <20220201180822.148370751@linuxfoundation.org>
> # Subject: [PATCH 4.4 00/25] 4.4.302-rc1 review # ...
> # NOTE!  This is the proposed LAST 4.4.y kernel release to happen under # the
> rules of the normal stable kernel releases.  After this one, it will # be marked
> End-Of-Life as it has been 6 years and you really should know # better by now
> and have moved to a newer kernel tree.  After this one, no # more security fixes
> will be backported and you will end up with an # insecure system over time.
> # ...
> # Responses should be made by Thu, 03 Feb 2022 18:08:10 +0000.
> # Anything received after that time might be too late.
> 
> (He sometimes releases kernels before the deadline).
> 
> We may want to make any announcements now or just after 4.4.302 is
> released... so I guess we should start working on suitable wording.
> 
> Something like:
> 
> CIP project is committed to maintain 4.4.x kernel till January of 2027 [1]. We are
> maintaining -cip branch [2], that is stable kernel with about
> 1000 of patches to support our reference hardware [3] and -cip-rt branch, with
> is merge of -rt and -cip trees.
> 
> If you for some reason need 4.4.x with bug and security fixes, and are running
> similar hardware to our reference hardware (x86-64 and armv7), -cip tree may
> be good base for that work. Testing of the -cip tree is welcome, as is joining the
> CIP project.
> 
> [1] https://wiki.linuxfoundation.org/civilinfrastructureplatform/start
> [2]
> https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linu
> x-4.4.y-cip-rt
> [3]
> https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/ciprefe
> rencehardware

Thank you for taking up the issue. I think the content is fine.
BTW, do you have any future information about the RT kernel team?
We may also need to check the RT patch.
If you don't have the information, I'll ask the RT team about this.

Best regards,
  Nobuhiro


> 
> ?
> 
> Best regards,
> 								Pavel
> --
> DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Re: [cip-dev] 4.4.302 is going to be last 4.4 release

[Jan Kiszka]

On 03.02.22 08:13, nobuhiro1.iwamatsu@toshiba.co.jp wrote:
> Hi Pavel,
>> -----Original Message-----
>> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
>> Behalf Of Pavel Machek
>> Sent: Wednesday, February 2, 2022 6:33 AM
>> To: jan.kiszka@siemens.com; cip-dev@lists.cip-project.org
>> Subject: [cip-dev] 4.4.302 is going to be last 4.4 release
>>
>> Hi!
>>
>> Greg says:
>>
>> # Message-Id: <20220201180822.148370751@linuxfoundation.org>
>> # Subject: [PATCH 4.4 00/25] 4.4.302-rc1 review # ...
>> # NOTE!  This is the proposed LAST 4.4.y kernel release to happen under # the
>> rules of the normal stable kernel releases.  After this one, it will # be marked
>> End-Of-Life as it has been 6 years and you really should know # better by now
>> and have moved to a newer kernel tree.  After this one, no # more security fixes
>> will be backported and you will end up with an # insecure system over time.
>> # ...
>> # Responses should be made by Thu, 03 Feb 2022 18:08:10 +0000.
>> # Anything received after that time might be too late.
>>
>> (He sometimes releases kernels before the deadline).
>>
>> We may want to make any announcements now or just after 4.4.302 is
>> released... so I guess we should start working on suitable wording.
>>
>> Something like:
>>
>> CIP project is committed to maintain 4.4.x kernel till January of 2027 [1]. We are
>> maintaining -cip branch [2], that is stable kernel with about
>> 1000 of patches to support our reference hardware [3] and -cip-rt branch, with
>> is merge of -rt and -cip trees.
>>
>> If you for some reason need 4.4.x with bug and security fixes, and are running
>> similar hardware to our reference hardware (x86-64 and armv7), -cip tree may
>> be good base for that work. Testing of the -cip tree is welcome, as is joining the
>> CIP project.
>>
>> [1] https://wiki.linuxfoundation.org/civilinfrastructureplatform/start
>> [2]
>> https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linu
>> x-4.4.y-cip-rt
>> [3]
>> https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/ciprefe
>> rencehardware
> 
> Thank you for taking up the issue. I think the content is fine.

Looks good to me as well.

Given that 4.4 is now history and Greg even mentioned CIP in his
discontinuation message [1] but said that we would only "consider" to
continue: Let's follow up on his post, only referring to the regular
linux-4.4.y-cip for now. Who of you two could do that?

> BTW, do you have any future information about the RT kernel team?
> We may also need to check the RT patch.
> If you don't have the information, I'll ask the RT team about this.
> 

Why should 4.4-rt continue if its former upstream retired?

Jan

[1] https://lkml.org/lkml/2022/2/3/91

-- 
Siemens AG, Technology
Competence Center Embedded Linux

RE: [cip-dev] 4.4.302 is going to be last 4.4 release

[Chris Paterson]

Hello,

> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of Jan Kiszka via lists.cip-project.org
> Sent: 06 February 2022 18:48
> 

[...]

> 
> > BTW, do you have any future information about the RT kernel team?
> > We may also need to check the RT patch.
> > If you don't have the information, I'll ask the RT team about this.
> >
> 
> Why should 4.4-rt continue if its former upstream retired?

Didn't CIP commit to maintaining a real-time version of each SLTS for the 10 years?

Kind regards, Chris

Re: [cip-dev] 4.4.302 is going to be last 4.4 release

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

Hi!

> > > BTW, do you have any future information about the RT kernel team?
> > > We may also need to check the RT patch.
> > > If you don't have the information, I'll ask the RT team about this.
> > 
> > Why should 4.4-rt continue if its former upstream retired?
> 
> Didn't CIP commit to maintaining a real-time version of each SLTS for the 10 years?

We did commit to maintaining 4.4-cip-rt, but upstream 4.4.X is going
to be discontinued, and so is 4.4.X-stable.

Best regards,
								Pavel

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

RE: [cip-dev] 4.4.302 is going to be last 4.4 release

[Chris Paterson]

> From: Pavel Machek <pavel@denx.de>
> Sent: 08 February 2022 15:36
> 
> Hi!
> 
> > > > BTW, do you have any future information about the RT kernel team?
> > > > We may also need to check the RT patch.
> > > > If you don't have the information, I'll ask the RT team about this.
> > >
> > > Why should 4.4-rt continue if its former upstream retired?
> >
> > Didn't CIP commit to maintaining a real-time version of each SLTS for the 10
> years?
> 
> We did commit to maintaining 4.4-cip-rt, but upstream 4.4.X is going
> to be discontinued, and so is 4.4.X-stable.

So does CIP need to maintain the stable version of RT as well as the non-RT stable kernel?
Is this achievable?

Regards, Chris

> 
> Best regards,
> 								Pavel
> 
> --
> DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Re: [cip-dev] 4.4.302 is going to be last 4.4 release

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

On Wed 2022-02-09 11:05:44, Chris Paterson wrote:
> > From: Pavel Machek <pavel@denx.de>
> > Sent: 08 February 2022 15:36
> > 
> > Hi!
> > 
> > > > > BTW, do you have any future information about the RT kernel team?
> > > > > We may also need to check the RT patch.
> > > > > If you don't have the information, I'll ask the RT team about this.
> > > >
> > > > Why should 4.4-rt continue if its former upstream retired?
> > >
> > > Didn't CIP commit to maintaining a real-time version of each SLTS for the 10
> > years?
> > 
> > We did commit to maintaining 4.4-cip-rt, but upstream 4.4.X is going
> > to be discontinued, and so is 4.4.X-stable.
> 
> So does CIP need to maintain the stable version of RT as well as the non-RT stable kernel?
> Is this achievable?

My understanding is that we are maintaining both 4.4-cip and
4.4-cip-rt going forward. I hope it is achievable.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]