public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: alex.kanavin@gmail.com
Cc: liuyd.fnst@fujitsu.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH v2] python3-roman-numerals-py: upgrade 3.1.0 -> 4.1.0
Date: Thu, 08 Jan 2026 09:52:00 +0000	[thread overview]
Message-ID: <1485ed48426d8d8c9995bab35925fab65591b176.camel@pbarker.dev> (raw)
In-Reply-To: <CANNYZj-=U+tTgqr58uDuj=vmC57Uj8d4WGvz7n5=8uYyOoUCVQ@mail.gmail.com>

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

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
> <paul=pbarker.dev@lists.openembedded.org> 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


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2026-01-08  9:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08  1:41 [OE-core][PATCH v2] python3-roman-numerals-py: upgrade 3.1.0 -> 4.1.0 Liu Yiding
2026-01-08  9:46 ` Paul Barker
2026-01-08  9:49   ` Alexander Kanavin
2026-01-08  9:52     ` Paul Barker [this message]
2026-01-08 11:35 ` Mathieu Dubois-Briand
2026-01-09  9:35   ` 回复: " Yiding Liu (Fujitsu)
2026-01-09 10:02     ` Alexander Kanavin

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=1485ed48426d8d8c9995bab35925fab65591b176.camel@pbarker.dev \
    --to=paul@pbarker.dev \
    --cc=alex.kanavin@gmail.com \
    --cc=liuyd.fnst@fujitsu.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