public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com, Anton Mikanovich <amikan@ilbers.de>,
	"Kowalsky,
	Clara (FT RPD CED OES-DE)" <clara.kowalsky@siemens.com>
Subject: Re: Decide on official Isar release cycle
Date: Tue, 16 Dec 2025 14:14:18 +0100	[thread overview]
Message-ID: <6ca2662c-d653-4a28-b8a3-2725b9819087@siemens.com> (raw)
In-Reply-To: <aUFQQHaBVLXEtIdF@abai.de>

On 16.12.25 13:27, Baurzhan Ismagulov wrote:
> On 2025-12-16 12:36, 'Jan Kiszka' via isar-users wrote:
>>> We could think about starting with two releases per year, gaining experience
>>> (esp. regarding larger code changes) and seeing which effort it requires.
>>
>> That's the absolute minimum, but will likely not change a lot
>> downstream, at least as long as we find too many issues via the
>> downstream layers, thus potentially to late for a release.
> 
> Ok, let me understand.
> 
> cip-core wants quarterly Isar releases -- good to know.
> What is the cycle?
> 
> Do I understand correctly, if Isar would do quarterly releases, cip-core would
> use Isar tags?

At least, we would try to align then. There can always be reasons to
slightly deviate in concrete case, but so far I was preferring a newer
Isar revision with local, upstream-pending hot-fixes over older Isar
revisions. That is because I know downstream will do own integration
decisions, and the more freedom isar-cip-core can provide by being
compatible with more recent Isar versions, the better.

Not too infrequently, we are also developing Isar features to cater
developments in isar-cip-core, and it is much nicer to consume them via
upstream rather than out-of-tree patches in our layer.

> Then it would go downstream, Isar issues would be found and fixed (which
> suggests extending Isar testsuite).
> Is your point that the next Isar release a quarter later would be soon enough
> for the downstreams?
> 
> In any case, we could still try 1.1 in 2026-Q3 and then revisit this topic.
> 

2 release per year would be an improvement, and we can try this if you
consider it a reasonable balance between stabilization effort on the one
side and community value on the other.

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/6ca2662c-d653-4a28-b8a3-2725b9819087%40siemens.com.

  reply	other threads:[~2025-12-16 13:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16  7:37 'Clara Kowalsky' via isar-users
2025-12-16  7:58 ` 'Jan Kiszka' via isar-users
2025-12-16  7:58 ` Anton Mikanovich
2025-12-16  8:06   ` 'Jan Kiszka' via isar-users
2025-12-16 10:53     ` Baurzhan Ismagulov
2025-12-16 11:36       ` 'Jan Kiszka' via isar-users
2025-12-16 12:27         ` Baurzhan Ismagulov
2025-12-16 13:14           ` 'Jan Kiszka' via isar-users [this message]
2025-12-16 11:42       ` 'Andreas Naumann' via isar-users
2025-12-16 11:28     ` 'Andreas Naumann' via isar-users

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=6ca2662c-d653-4a28-b8a3-2725b9819087@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=amikan@ilbers.de \
    --cc=clara.kowalsky@siemens.com \
    --cc=jan.kiszka@siemens.com \
    /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