On Mon, 2026-05-18 at 13:55 +0800, [email protected] wrote: > From: Chen Qi <[email protected]> > > We want the ability to do stable version upgrades for recipes. > To this end, add an optional stable_upgrade parameter to the > get_recipe_upgrade_status function, which defaults to False and > when enabled will try to get the latest stable version of the recipe. > > The UPSTREAM_STABLE_RELEASE_REGEX is respected. If a recipe sets > it, it will be used as the filter_regex. If it's not set explicitly, > it means that there's no stable updates or the recipe hasn't been > checked yet. > > Signed-off-by: Chen Qi <[email protected]>
Hi Qi, We discussed this series on the patch review call. The implementation here looks good and we're broadly in favour of this approach. But, before we merge this we need to: - confirm how this will be used on the stable branch - agree what criteria we judge upstream stable branches against - get buy-in from the stable maintainer As this will alter our policy of how we handle stable recipe updates, someone needs to send a proposal to the openembedded-architecture list. If you can send the initial email to the architecture list with how you see this working, I'm happy to provide feedback and drive the discussion forwards. Best regards, -- Paul Barker
signature.asc
Description: This is a digitally signed message part
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#237503): https://lists.openembedded.org/g/openembedded-core/message/237503 Mute This Topic: https://lists.openembedded.org/mt/119368636/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
