From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: Re: Reminder: hotfix fast path needed
Date: Thu, 23 Oct 2025 12:42:13 +0200 [thread overview]
Message-ID: <aPoGhetfr5ORsjQJ@abai.de> (raw)
In-Reply-To: <3c21e4e1-ad2b-4510-8cf2-ba616fc166dc@siemens.com>
Hello Jan,
On 2025-10-23 07:52, Jan Kiszka wrote:
> Patches that carry "Fixes:" tag and address build breakages should be on
> a fast path for QA and merge. I'm pointing colleagues to [1] and [2]
> almost on a daily basis, but those are just two recent examples.
>
> [1] https://patchwork.isar-build.org/project/isar/patch/20251017085344.2647058-1-felix.moessbauer@siemens.com/
> [2] https://patchwork.isar-build.org/project/isar/patch/0f16240d-aca7-4f03-b0f7-1567c5b4c26f@siemens.com/
I acknowledge the desire to have fast path for "Fixes:" and build breakages.
We've merged #2. The full results for #1 will be available tomorrow. There is a
number of failures due to e.g. external networking issues; we'll be sharing
patches for those.
I think introducing fast path for certain changes is the easiest part of the
equation. In #2, you also express regret that there is no testcase for the
feature in question. In general, we should think about adding testcases on use
case introduction and bug fixes -- here I agree with Cedric. I think this has
larger contribution to the quality, benefits all downstreams and saves the
overall fixing effort, as every applied change could break the feature. Once a
fix goes in, a testcase never follows. Currently, we are developing testcases
for certain changes from the list; longer-term, this will not work.
The Linux "tested by many" model helps only to some extent. We also see e.g.
conflicting changes being applied back and forth, even in Linux. Having the use
case view backed by tests at the Isar level would avoid this.
To summarize, we'll evaluate this proposal and also invite for more
collaboration on testcases.
With kind regards,
Baurzhan
--
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/aPoGhetfr5ORsjQJ%40abai.de.
next prev parent reply other threads:[~2025-10-23 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 5:52 'Jan Kiszka' via isar-users
2025-10-23 10:42 ` Baurzhan Ismagulov [this message]
2025-10-23 11:05 ` 'MOESSBAUER, Felix' via isar-users
2025-10-24 11:23 ` 'MOESSBAUER, Felix' via isar-users
2025-10-24 11:54 ` 'cedric.hombourger@siemens.com' 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=aPoGhetfr5ORsjQJ@abai.de \
--to=ibr@radix50.net \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.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