linux-kernel - Re: [PATCH] docs: Update version number from 5.x to 6.x in README.rst

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 25 Aug 2022 09:27:51 +0200
From:   Lukas Bulwahn <lukas.bulwahn@...il.com>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     Jonathan Corbet <corbet@....net>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Tony Fischetti <tony.fischetti@...il.com>,
        Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH] docs: Update version number from 5.x to 6.x in README.rst

On Thu, Aug 25, 2022 at 5:08 AM Bagas Sanjaya <bagasdotme@...il.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