From: "Siddharth Doshi" <sdoshi@mvista.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [master][scarthgap][PATCH] wpa-supplicant: Upgrade 2.10 -> 2.11
Date: Fri, 23 Aug 2024 10:17:59 -0700 [thread overview]
Message-ID: <5008.1724433479274681997@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj_k-QHOXH-qEu69HTBcza1d3zge6LQkH5JmbxWYmyJVtw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
Hi Randy and Alex,
I appreciate the feedback and your concern regarding upgrades in stable-branches.
>
> This update make sense for the master brnanch but likely not for scarthgap
> unless you can show that
> this is a bug fix only release.
>
- This release for sure is not a bug fix only release. It does include support to new feature and can never classify as bug fix only release.
>
> you'll have to backport any CVE fixes that you're interested in unless
> someone explains why this is a sensible update for scarthgap.
>
>
- I do the understand that upgrades are avoided in stable/LTS branches as it might break the compatibility and result in various compilation issues.
- However, that would only take place if the backward compatibility of the new upgrade is questionable.
- Generally every new releases will have API or ABI-symbols added but if API or ABI symbols are removed from shared libraries or binaries it a matter of concern as it would be the cause of breakdown.
- For this release, there are no ABI-symbols or API removed from the binaries and shared libraries. you can cross-check it in different ways (there are open-source tools to check or can be checked by manually comparing the header files)
- I have my own script to do so and i always check the backward compatibility before submitting any upgrades and since it was all clear for wpa-supplicant, i went ahead with the upgrade.
However, if still the opinion is that upgrade should be avoided, let me know, i would submit the CVE-patch for the same.
Regards,
Siddharth
[-- Attachment #2: Type: text/html, Size: 6695 bytes --]
next prev parent reply other threads:[~2024-08-23 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 16:17 [OE-core][master][scarthgap][PATCH] wpa-supplicant: Upgrade 2.10 -> 2.11 Siddharth
2024-08-23 0:56 ` Randy MacLeod
2024-08-23 15:59 ` Viswanath Kraleti
2024-08-23 16:39 ` Alexander Kanavin
2024-08-23 17:17 ` Siddharth Doshi [this message]
2024-08-23 17:21 ` [OE-core] [master][scarthgap][PATCH] " Alexander Kanavin
2024-08-23 17:32 ` Siddharth Doshi
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=5008.1724433479274681997@lists.openembedded.org \
--to=sdoshi@mvista.com \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox