Re: Decide on official Isar release cycle

["'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>]

On 16.12.25 08:37, Clara Kowalsky wrote:
> Hi,
> 
> last week at the Isar Community Meetup, the desire was expressed to
> finally have a v1.0 Isar release to demonstrate project maturity, as
> well as to have more releases per year, ideally quarterly.

Thanks for reminding of this fairly important topic.

> So far, the approach has been to release approximately one minor release
> per year, which brings us to v0.11 at present.
> My suggestion would be to follow a similar approach as Debian and have a
> major release every two years, along with a minor release every quarter.
> 
> How should we proceed? Which strategy do we want to establish?
> Ideally, we could release the first major version in January and then
> proceed with a quarterly cycle.

In contrast to Debian, there is no stable branch strategy for Isar in
sight, is there? In that light, I would just go for a time-driven
quarterly release with accordingly named tags, e.g.

2026.01, 2026.04, 2026.07, 2026.10

or "v2026.01" if preferred to start with a letter.

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/9e7cf017-ebae-466f-bafb-f5fbde69fd4f%40siemens.com.