On Thu, 2026-01-08 at 10:49 +0100, Alexander Kanavin via lists.openembedded.org wrote: > On Thu, 8 Jan 2026 at 10:46, Paul Barker via lists.openembedded.org > <[email protected]> wrote: > > As a side note, when we upgrade a recipe across multiple upstream > > versions we should include the changelog entries in our commit message > > for each version we skip across, especially if there's a major version > > bump in there as it's often because of some backwards incompatibility. > > I'd clarify this a bit: either there's a complete changelog for each > in-between version, or no changelog at all. It can be tedious to > produce them, especially if there's a lot of recipes updates in a > patchset, and it's not a strict requirement.
You're right, it can be tedious. We need to be careful in cases like this where an upgrade from v3.1 to v4.1 skips over a v4.0 major version with significant things in the release notes. 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 (#229052): https://lists.openembedded.org/g/openembedded-core/message/229052 Mute This Topic: https://lists.openembedded.org/mt/117146022/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
