From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Zhihang Wei <wzh@ilbers.de>,
Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com, Baurzhan Ismagulov <ibr@ilbers.de>
Cc: quirin.gylstorff@siemens.com
Subject: Re: [PATCH 0/2] Rework deployment of image artifacts
Date: Thu, 16 Apr 2026 18:01:39 +0200 [thread overview]
Message-ID: <59c17c07-b886-47d5-b022-bb996f3606c2@siemens.com> (raw)
In-Reply-To: <a4f2b187-15f8-4ffa-9f1a-a2b86c36b458@siemens.com>
On 16.04.26 17:51, Jan Kiszka wrote:
> On 16.04.26 17:42, Zhihang Wei wrote:
>> Applied to next, thanks.
>>
>
> I am repeating myself: We broken the deployment API in v1.0. This series
> is breaking it once more, just differently (and rather unhandy for many
> downstream users).
>
> Are we truly sure now that this is the FINAL solution, or do we plan for
> n more API breakages?
>
But let's a assume we keep it like this:
What is the plan for a v1.0.1 hotfix release? I'm seeing other patches
being merged. Some would qualify to be part as well, another one is
harmless but not a hotfix. So I'm asking before things possibly move on
further. At least some users here are waiting to adopt v1.0.x.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/59c17c07-b886-47d5-b022-bb996f3606c2%40siemens.com.
next prev parent reply other threads:[~2026-04-16 16:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 13:22 'Felix Moessbauer' via isar-users
2026-04-10 13:22 ` [PATCH 1/2] Revert "meta: Deploy image build artifacts into distro- and image-specific subdirs" 'Felix Moessbauer' via isar-users
2026-04-10 13:22 ` [PATCH 2/2] prefix DTB files with PN in deploy dir 'Felix Moessbauer' via isar-users
2026-04-10 13:38 ` 'Jan Kiszka' via isar-users
2026-04-10 14:12 ` 'MOESSBAUER, Felix' via isar-users
2026-04-10 16:32 ` 'Jan Kiszka' via isar-users
2026-04-16 13:54 ` Zhihang Wei
2026-04-16 14:39 ` 'MOESSBAUER, Felix' via isar-users
2026-04-16 15:41 ` Zhihang Wei
2026-04-10 14:21 ` [PATCH 0/2] Rework deployment of image artifacts Zhihang Wei
2026-04-16 15:42 ` Zhihang Wei
2026-04-16 15:51 ` 'Jan Kiszka' via isar-users
2026-04-16 16:01 ` 'Jan Kiszka' via isar-users [this message]
2026-04-17 14:15 ` Zhihang Wei
2026-04-17 14:39 ` 'Jan Kiszka' via isar-users
2026-04-17 15:05 ` 'Jan Kiszka' via isar-users
2026-04-20 6:25 ` 'Quirin Gylstorff' via isar-users
2026-04-20 16:00 ` Zhihang Wei
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=59c17c07-b886-47d5-b022-bb996f3606c2@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=ibr@ilbers.de \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.com \
--cc=wzh@ilbers.de \
/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