linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Tony Fischetti <tony.fischetti@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] docs: Update version number from 5.x to 6.x in README.rst
Date: Thu, 25 Aug 2022 09:27:51 +0200	[thread overview]
Message-ID: <CAKXUXMwTP1KMq1HEoNyR-vRzQYYoTHEumZBu3-urEM8P9r=iWA@mail.gmail.com> (raw)
In-Reply-To: <df8c22fb-878a-3d98-4a9d-9000b4a2ffa7@gmail.com>

On Thu, Aug 25, 2022 at 5:08 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> On 8/24/22 15:08, Lukas Bulwahn wrote:
> > The description in 2.Process.rst is just a description of recent kernel
> > releases, it was last updated in the beginning of 2020, and can be
> > revisited at any time on a regular basis, independent of changing the
> > version number from 5 to 6. So, there is no need to update this document
> > now when transitioning from 5.x to 6.x numbering.
> >
> The drawback of having quick list of recent kernel releases in 2.Process.rst
> is that the list can be quickly outdated with newer releases, unless the list
> is updated for every upcoming merge window.
>
> There are two options:
>
>   1. Programmatically generate the list, using last 5 mainline releases
>      from Linus's tree, or
>   2. Simply point to kernel.org frontpage
>

As the commit message says, this patch here only touches the README.rst.
The commit message of course also explains why the rest was not
touched, and sure, we can discuss if and how to improve those parts,
but I would like to get an ack on the actual patch first and get that
merged.

So to 2.Process.rst, writing a script to generate the list is
possible, but it is already quite clear that just says "recent", which
is vague anyway. In a software project that is older than 30 years,
"recent" is certainly a bit more relaxed than some other SW project
that just started yesterday.

As it is documentation to convince a new developer, it might be better
to just describe how a new developer can check that the releases are
done very predictable. So, we explain the commands for the reader to
check if he/she/they want to convince themselves.

Lukas

  reply	other threads:[~2022-08-25  7:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  8:08 [PATCH] docs: Update version number from 5.x to 6.x in README.rst Lukas Bulwahn
2022-08-25  3:08 ` Bagas Sanjaya
2022-08-25  7:27   ` Lukas Bulwahn [this message]
2022-08-25  3:24 ` Randy Dunlap
2022-08-25  7:35   ` Lukas Bulwahn
2022-08-25  7:39     ` Randy Dunlap
2022-08-25  7:53     ` Bagas Sanjaya
2022-08-25 18:48 ` Jonathan Corbet
2022-08-26  2:19   ` Bagas Sanjaya
2022-08-26  2:24     ` Randy Dunlap
2022-08-26 13:18     ` Jonathan Corbet
2022-08-26  8:28   ` Bagas Sanjaya

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='CAKXUXMwTP1KMq1HEoNyR-vRzQYYoTHEumZBu3-urEM8P9r=iWA@mail.gmail.com' \
    --to=lukas.bulwahn@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tony.fischetti@gmail.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;
as well as URLs for NNTP newsgroup(s).