From: <daniel.turull@ericsson.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Daniel Turull <daniel.turull@ericsson.com>
Subject: [PATCH 0/3] devtool: add changelog extraction
Date: Tue, 12 May 2026 09:24:43 +0200 [thread overview]
Message-ID: <20260512072446.2323529-1-daniel.turull@ericsson.com> (raw)
From: Daniel Turull <daniel.turull@ericsson.com>
This series aims to extract the changelog between 2 versions when
devtool is upgrade. The aim is that later to backport the feature into
LTS branches, so we can have more detailed descriptions with AUH.
For testing I reverted the last 200 updates of recipes and master and
try to do devtool upgrade <recipe> --no-patch, since I'm only interested
in the changelog output.
From the last run: 83 with changelog, 21 without, 41 failed.
Excluding failures: 83 out of 104 = 80% of changelog were generated.
Daniel Turull (3):
devtool: upgrade: extract changelog between versions
devtool: upgrade: detect per-version release notes files
devtool: upgrade: clean up extracted changelog content
meta/lib/oeqa/selftest/cases/devtool.py | 24 +++++++
scripts/lib/devtool/standard.py | 8 +++
scripts/lib/devtool/upgrade.py | 95 +++++++++++++++++++++++++
3 files changed, 127 insertions(+)
--
2.34.1
next reply other threads:[~2026-05-12 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 7:24 daniel.turull [this message]
2026-05-12 7:24 ` [PATCH 1/3] devtool: upgrade: extract changelog between versions daniel.turull
2026-05-12 16:28 ` [OE-core] " Alexander Kanavin
2026-05-13 7:26 ` Daniel Turull
2026-05-12 7:24 ` [PATCH 2/3] devtool: upgrade: detect per-version release notes files daniel.turull
2026-05-12 7:24 ` [PATCH 3/3] devtool: upgrade: clean up extracted changelog content daniel.turull
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=20260512072446.2323529-1-daniel.turull@ericsson.com \
--to=daniel.turull@ericsson.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 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.