From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: Zhihang Wei <wzh@ilbers.de>, isar-users <isar-users@googlegroups.com>
Subject: Re: Isar v1.0 Release
Date: Tue, 7 Apr 2026 12:56:24 +0000 [thread overview]
Message-ID: <7cf5df0e86979f542f0588d159988d2af14ff6b9.camel@siemens.com> (raw)
In-Reply-To: <c0a31a66-84c0-4bf5-8424-979ee0caefd8@ilbers.de>
On Thu, 2026-04-02 at 18:06 +0200, Zhihang Wei wrote:
> Hi everyone,
>
> I have just tagged the release of Isar v1.0.
Hi, thanks for creating the release and also signing the tag.
I'm just wondering why significant changes like "trixie: Workaround
with missing drivers in initramfs" and "Deploy DTBs and other image
artifacts into subdirs to avoid conflicts" were merged only minutes
before the release was cut.
Especially for the "Deploy DTBs" change (which requires downstream
testing) I expected to get another release candidate.
Along that, the release was tagged on next instead of master which also
is a bit unexpected.
Best regards,
Felix
--
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/7cf5df0e86979f542f0588d159988d2af14ff6b9.camel%40siemens.com.
next prev parent reply other threads:[~2026-04-07 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 16:06 Zhihang Wei
2026-04-07 12:36 ` 'Quirin Gylstorff' via isar-users
2026-04-07 12:56 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-04-07 14:37 ` Roberto A. Foglietta
2026-04-07 15:18 ` 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=7cf5df0e86979f542f0588d159988d2af14ff6b9.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@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