From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Guenter Roeck <linux@roeck-us.net>,
Steven Rostedt <rostedt@goodmis.org>,
"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: [TECH TOPIC] regressions: our workflows are the biggest enemy
Date: Wed, 12 Jun 2024 14:35:19 -0400 [thread overview]
Message-ID: <f6kqhk72iujjugt3nb7wsiz523meti6hnfzptukjpqjvkybckv@e32yogihxcch> (raw)
In-Reply-To: <47793732-03f6-4cbb-a2a4-393ad9c96de9@leemhuis.info>
* Thorsten Leemhuis <linux@leemhuis.info> [240612 12:08]:
> On 12.06.24 17:50, Guenter Roeck wrote:
> > On 6/12/24 08:26, 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.
>
> Stuff for the maintainers summit is still in my editor.
>
> >> If you have real numbers that point out workflows that are an issue,
>
> No, I sadly do not. And they would be flawed anyway, as there are many
> regressions I never become aware of -- and it's not really possible to
> determine from commits if they were fixing a regression or not. So it
> could easily be possible that I only see the bad cases and miss out on a
> lot of cases that a subsystem handles well. Not to mention that I
> currently miss out on a most DRM bugs, as they use a external bug
> tracker. Regzbot can monitor that now, but I have no easy means to
> become aware of regressions reported there. The idea was to start vising
> a handful of issue trackers every day or two and use a boring search,
> but as of now that's still an unrealized plan.
>
> >> I think this should be discussed
> >> at Maintainers Summit, and perhaps we should start "encouraging" people
> >> to change their workflows. Especially if we have hard data showing
> >> that it's not working.
That would limit the number of people who can see this discussion as not
all maintainers are at the Maintainers Summit. I suspect that the ones
that are not at the Maintainers Summit will be the same ones who will
benefit most from workflow "encouraging".
Although, I'm a little concerned about what I'm singing up for here...
Thanks,
Liam
next prev parent reply other threads:[~2024-06-12 18:35 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 [this message]
2024-06-13 10:32 ` Thorsten Leemhuis
2024-06-12 18:37 ` Leon Romanovsky
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=f6kqhk72iujjugt3nb7wsiz523meti6hnfzptukjpqjvkybckv@e32yogihxcch \
--to=liam.howlett@oracle.com \
--cc=ksummit@lists.linux.dev \
--cc=linux@leemhuis.info \
--cc=linux@roeck-us.net \
--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