All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: "open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	workflows@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [RFC PATCH v1 1/2] docs: add a document about regression handling
Date: Wed, 5 Jan 2022 09:45:57 +0100	[thread overview]
Message-ID: <CAKXUXMwJU2vZp2C8Q6xEUCgKox2z_Qt5gH_UpSa5BJiVeRkoyg@mail.gmail.com> (raw)
In-Reply-To: <72fcaa40-5884-710f-58b6-bf40a1f58e57@leemhuis.info>

On Tue, Jan 4, 2022 at 6:57 PM Thorsten Leemhuis <linux@leemhuis.info> wrote:
>
>
> On 04.01.22 15:17, Lukas Bulwahn wrote:
> > On Mon, Jan 3, 2022 at 3:23 PM Thorsten Leemhuis <linux@leemhuis.info> wrote:
> >>
> >> Create a document explaining various aspects around regression handling
> >> and tracking both for users and developers. Among others describe the
> >> first rule of Linux kernel development and what it means in practice.
> >> Also explain what a regression actually is and how to report them
> >> properly. The text additionally provides a brief introduction to the bot
> >> the kernel's regression tracker users to facilitate the work. To sum
> >> things up, provide a few quotes from Linus to show how serious the he
> >> takes regressions.
> >>
> >> [...]
> >
> > [lots of helpful suggestions for fixes and small improvements]
>
> Many thx, addressed all of them, not worth commenting on each of them
> individually.
>
>
> >> +What is the goal of the 'no regressions rule'?
> >> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >> +
> >> +Users should feel safe when updating kernel versions and not have to worry
> >> +something might break. This is in the interest of the kernel developers to make
> >> +updating attractive: they don't want users to stay on stable or longterm Linux
> >> +series either abandoned or more than one and a half year old, as `those might
> >> +have known problems, security issues, or other aspects already improved in later
> >> +versions
> >> +<http://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/>`_.
> >> +
> > Maybe add something like this:
> >
> > A larger user community means more exposure and more confidence that
> > any critical bug introduced is likely to be found closer to the point
> > in time it was introduced, and hence the shipped kernels have less
> > critical bugs.
> >
> > Just to close the line of thought here.
>
> Hmmm. How about this instead:
>
> The kernel developers also want to make it simple and appealing for
> users to test the latest (pre-)release, as it's a lot easier to track
> down and fix problems, if they are reported shortly after being introduced.

Yes, your sentence conveys the same point and is much more down to
earth. My sentence looks much more "academic".

> > Okay, that is how far I got reading for now.
>
> Great, many thx for your help, much appreciated. FWIW, find below the
> current version of the plain text which contains a few more fixes. Note,
> thunderbird will insert wrong line breaks here.
>
> Ciao, Thorsten
>

All good, I will wait until the next version of this patch series shows up.

Lukas

  reply	other threads:[~2022-01-05  8:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  9:50 [RFC PATCH v1 0/2] docs: add a document dedicated to regressions Thorsten Leemhuis
2022-01-03  9:50 ` [RFC PATCH v1 1/2] docs: add a document about regression handling Thorsten Leemhuis
2022-01-03 17:07   ` Jakub Kicinski
2022-01-03 17:20     ` Thorsten Leemhuis
2022-01-03 17:55       ` Jakub Kicinski
2022-01-04 14:17   ` Lukas Bulwahn
2022-01-04 17:57     ` Thorsten Leemhuis
2022-01-05  8:45       ` Lukas Bulwahn [this message]
2022-01-03  9:50 ` [RFC PATCH v1 2/2] docs: regressions.rst: rules of thumb for handling regressions Thorsten Leemhuis
2022-01-04 12:16   ` Lukas Bulwahn
2022-01-04 13:29     ` Thorsten Leemhuis
2022-01-04 14:42       ` Jonathan Corbet
2022-01-04 15:09         ` Randy Dunlap
2022-01-04 18:02           ` Thorsten Leemhuis
2022-01-03 14:01 ` [RFC PATCH v1 0/2] docs: add a document dedicated to regressions Greg Kroah-Hartman

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=CAKXUXMwJU2vZp2C8Q6xEUCgKox2z_Qt5gH_UpSa5BJiVeRkoyg@mail.gmail.com \
    --to=lukas.bulwahn@gmail.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=workflows@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.