From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: kaloyan.rusev@elektrobit.com
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][wrynose][PATCH] ankaios: add Eclipse Ankaios container orchestrator recipe at v1.0.3
Date: Wed, 16 Sep 2026 07:07:31 -0700 (PDT) [thread overview]
Message-ID: <6aaaa2a3.98235939.208b75.d30f@mx.google.com> (raw)
In-Reply-To: <20260915122238.1558501-1-kaloyan.rusev@elektrobit.com>
Hi Kaloyan,
Two things on this one!
First, same issue as the master-branch v1.0.3 update: the patch has no
Signed-off-by trailer. The body ends and jumps straight to the diff
separator. Please resend as v2 with:
Signed-off-by: Kaloyan Rusev <kaloyan.rusev@elektrobit.com>
on the last line of the commit body.
Second .. the decision on a backport. The normal stable-branch policy
is only 3rd-digit bugfix and security bumps. New functionality doesn't
land on old release branches, since that's where downstream users have
set their expectations. A new recipe is more than a version bump.
That said, I confirmed the risk is zero here: there is no
recipes-containers/ankaios/ on wrynose today, nothing else in the
wrynose tree references ankaios (no IMAGE_INSTALL, no RDEPENDS, no
packagegroup), and the patch is 100% additive. There's no path by
which merging this could break anything else in the layer.
I'd rather meta-virtualization be useful as a collaboration point when
the risk is that clean, so I lean toward taking this once the
Signed-off-by is in. Just want to be explicit that this is an
exception rather than the norm for stable.
Resend with the SoB and I'll take it.
Bruce
next prev parent reply other threads:[~2026-09-16 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 12:08 [meta-virtualization][wrynose][PATCH] ankaios: add Eclipse Ankaios container orchestrator recipe at v1.0.3 kaloyan.rusev
2026-09-16 14:07 ` Bruce Ashfield [this message]
2026-09-17 13:47 ` [meta-virtualization][wrynose][PATCH] ankaios: add Eclipse Ankaios container orchestrator recipe kaloyan.rusev
2026-09-23 16:10 ` Bruce Ashfield
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=6aaaa2a3.98235939.208b75.d30f@mx.google.com \
--to=bruce.ashfield@gmail.com \
--cc=kaloyan.rusev@elektrobit.com \
--cc=meta-virtualization@lists.yoctoproject.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.