From: Robert Yang <liezhi.yang@windriver.com>
To: Steve Sakoman <steve@sakoman.com>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
"alex.kanavin@gmail.com" <alex.kanavin@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/1] openssl: 3.4.2 -> 3.5.2
Date: Mon, 22 Sep 2025 23:23:27 +0800 [thread overview]
Message-ID: <cdfe72a9-87a4-431f-9f27-e29a1298f434@windriver.com> (raw)
In-Reply-To: <CAOSpxda7Jdtm0ewuCQ2JSoF_E7r6NKs--q1_4YUa6GsWUof7OA@mail.gmail.com>
On 9/22/25 21:57, Steve Sakoman wrote:
> On Sun, Sep 21, 2025 at 8:19 AM Robert Yang via lists.openembedded.org
> <liezhi.yang=windriver.com@lists.openembedded.org> wrote:
>>
>>
>>
>> On 9/19/25 22:00, Peter Kjellerstedt wrote:
>>>> -----Original Message-----
>>>> From: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org> On Behalf Of Alexander Kanavin via lists.openembedded.org
>>>> Sent: den 19 september 2025 12:21
>>>> To: liezhi.yang@windriver.com
>>>> Cc: openembedded-core@lists.openembedded.org
>>>> Subject: Re: [OE-core] [PATCH 1/1] openssl: 3.4.2 -> 3.5.2
>>>>
>>>> On Fri, 19 Sept 2025 at 04:55, Robert Yang via lists.openembedded.org <liezhi.yang=windriver.com@lists.openembedded.org> wrote:
>>>>> The benefit of OpenSSL 3.5 is that it is an LTS supported to 2030, which can
>>>>> save the maintenance time in the long run.
>>>>
>>>> Yes, and it also add new features, breaking the promise the project
>>>> makes to its users.
>>>>
>>>> This update cannot be done without TSC approval. You need to get that
>>>> first.
>>>>
>>>> Alex
>>>
>>> Also, this proposal was for Walnascar, which will be EoL after the
>>> next release (or two). Thus updating OpenSSL to a new minor version
>>> now makes no sense.
>> > > If it had been suggested for Scarthgap and the meta-lts-mixins layer,
>>> then I would have more understood it.
>>
>> I haven't tested it for Scarthgap, I think we need do it firstly for Walnascar,
>> then Scarthgap if it works.
>
> I will be building the final walnascar release on Friday.
>
> I don't feel comfortable doing this just prior to EOL with minimal
> testing and bake time.
>
> The TSC can of course decide to do it, but I'd push for scheduling at
> least one more release afterwards to deal with any breakage.
Yes, delay it makes sense to me.
// Robert
>
> Steve
>
>>
>> // Robert
>>
>>>
>>> //Peter
>>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#223801): https://lists.openembedded.org/g/openembedded-core/message/223801
>> Mute This Topic: https://lists.openembedded.org/mt/115322467/3620601
>> Group Owner: openembedded-core+owner@lists.openembedded.org
>> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [steve@sakoman.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
next prev parent reply other threads:[~2025-09-22 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 2:55 [walnascar][PATCH 0/1] openssl: 3.4.2 -> 3.5.2 liezhi.yang
2025-09-19 2:55 ` [PATCH 1/1] " liezhi.yang
2025-09-19 10:21 ` [OE-core] " Alexander Kanavin
2025-09-19 14:00 ` Peter Kjellerstedt
2025-09-21 15:19 ` Robert Yang
2025-09-22 13:57 ` Steve Sakoman
2025-09-22 15:23 ` Robert Yang [this message]
2025-09-21 15:15 ` Robert Yang
2025-09-24 18:31 ` Randy MacLeod
2025-09-26 6:15 ` Robert Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cdfe72a9-87a4-431f-9f27-e29a1298f434@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=steve@sakoman.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.