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]
Message-ID: <CAKwvOd=L7i6iMZ6CRKWpY1yzg5QZj5FM7Rd1HtVFj-6J-qdPtQ@mail.gmail.com>
Date:   Mon, 17 Oct 2022 17:04:55 -0700
From:   Nick Desaulniers <ndesaulniers@...gle.com>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        stable@...r.kernel.org, Ben Hutchings <ben@...adent.org.uk>,
        Sasha Levin <sashal@...nel.org>, Tyler Hicks <code@...icks.com>
Subject: Re: [PATCH v2] Documentation: process: replace outdated LTS table w/ link

On Fri, Oct 14, 2022 at 7:06 PM Bagas Sanjaya <bagasdotme@...il.com> wrote:
>
> On 10/15/22 00:10, Nick Desaulniers wrote:
> > The existing table was a bit outdated.
> >
> > 3.16 was EOL in 2020.
> > 4.4 was EOL in 2022.
> >
> > 5.10 is new in 2020.
> > 5.15 is new in 2021.
> >
> > We'll see if 6.1 becomes LTS in 2022.
> >
> > Rather than keep this table updated, it does duplicate information from
> > multiple kernel.org pages. Make one less duplication site that needs to
> > be updated and simply refer to the kernel.org page on releases.
> >
> > Suggested-by: Tyler Hicks <code@...icks.com>
> > Suggested-by: Bagas Sanjaya <bagasdotme@...il.com>
> > Signed-off-by: Nick Desaulniers <ndesaulniers@...gle.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>
> Should this patch be backported to all stable releases? I see Cc: stable
> on message header, but not in the patch trailer.

I don't think so; unless people read stable versions of the
documentation rather than HEAD?
Perhaps I didn't need to cc stable, but I think that's ok for
notifying people who are interested in stable, not necessarily
strictly for backports?
Either way, thanks again for the reviews+suggestions.

>
> >  Some kernels are designated "long term" kernels; they will receive support
> > -for a longer period.  As of this writing, the current long term kernels
> > -and their maintainers are:
> > -
> > -     ======  ================================        =======================
> > -     3.16    Ben Hutchings                           (very long-term kernel)
> > -     4.4     Greg Kroah-Hartman & Sasha Levin        (very long-term kernel)
> > -     4.9     Greg Kroah-Hartman & Sasha Levin
> > -     4.14    Greg Kroah-Hartman & Sasha Levin
> > -     4.19    Greg Kroah-Hartman & Sasha Levin
> > -     5.4     Greg Kroah-Hartman & Sasha Levin
> > -     ======  ================================        =======================
> > +for a longer period.  Please refer to the following link for the list of active
> > +long term kernel versions and their maintainers:
> > +
> > +     https://www.kernel.org/category/releases.html
> >
>
> LGTM, thanks.
>
> Reviewed-by: Bagas Sanjaya <bagasdotme@...il.com>
>
> --
> An old man doll... just what I always wanted! - Clara
>


-- 
Thanks,
~Nick Desaulniers

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ