Isar v1.0 Release

[Zhihang Wei]

Hi everyone,

I have just tagged the release of Isar v1.0.

Best regards,
Zhihang

[Quirin Gylstorff]

On 4/2/26 6:06 PM, Zhihang Wei wrote:
> Hi everyone,
>
> I have just tagged the release of Isar v1.0.

I expected the tag v1.0 on the master branch not next.

Was it intentional to tag next and not master?

Quirin

>
> Best regards,
> Zhihang
>

[MOESSBAUER, Felix]

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

[Roberto A. Foglietta]

Felix, IMHO because this underlines an act of unilateral ownership:
who pays, buys. Right?

When you were in China for Siemens, did you visit the Huazhong
University of Science and Technology?

Best regards,
--
Roberto A. Foglietta
+49.176.274.75.661
+39.349.33.30.697

[Zhihang Wei]

On 4/7/26 14:56, MOESSBAUER, Felix wrote:
> 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.

Hi,
I announced in the v1.0-rc1 email that these patches would be included.
The DTB v8 patch was not merged before tagging v1.0-rc1 because I still
needed to add some documentation and then send it as v9. The initramfs
workaround patch was not included in rc1 because it is dependent on the
DTB v8 patch.

> Along that, the release was tagged on next instead of master which also
> is a bit unexpected.

In general, patches are merged into next first, and then applied to
master later if CI shows no errors. For this release, I have just
synced master with next.

Zhihang