From: Leon Romanovsky <leon@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: [TECH TOPIC] regressions: our workflows are the biggest enemy
Date: Wed, 12 Jun 2024 21:37:12 +0300 [thread overview]
Message-ID: <20240612183712.GF4966@unreal> (raw)
In-Reply-To: <20240612112622.21bf7c89@rorschach.local.home>
On Wed, Jun 12, 2024 at 11:26:22AM -0400, Steven Rostedt wrote:
> On Wed, 12 Jun 2024 08:34:42 +0200
> Thorsten Leemhuis <linux@leemhuis.info> wrote:
>
> > The talk among others will describe why some workflow patterns are what
> > frequently leads to regressions -- and why they are also a factor why
> > some subsystems fix regression quickly, while others take weeks or
> > months to resolve.
>
> The above looks more than a TECH TOPIC. If you have real numbers that
> point out workflows that are an issue, I think this should be discussed
> at Maintainers Summit, and perhaps we should start "encouraging" people
> to change their workflows.
This topic is very interesting to whole Linux kernel community, and I think
it should be presented in the main track and not limited to Maintainers Summit.
Especially if you want "to encourage people to change their workflows".
Thanks
prev parent reply other threads:[~2024-06-12 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 6:34 Thorsten Leemhuis
2024-06-12 15:26 ` Steven Rostedt
2024-06-12 15:50 ` Guenter Roeck
2024-06-12 16:07 ` Thorsten Leemhuis
2024-06-12 18:35 ` Liam R. Howlett
2024-06-13 10:32 ` Thorsten Leemhuis
2024-06-12 18:37 ` Leon Romanovsky [this message]
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=20240612183712.GF4966@unreal \
--to=leon@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=linux@leemhuis.info \
--cc=rostedt@goodmis.org \
/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