mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "brookxu.cn@gmail.com" <brookxu.cn@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Choose 5.10 LTS or 5.15 LTS
Date: Mon, 8 Aug 2022 05:36:43 +0200	[thread overview]
Message-ID: <20220808033643.GB7325@1wt.eu> (raw)
In-Reply-To: <61ecca29-2d01-af2d-3d18-62dad41c63b4@gmail.com>

On Mon, Aug 08, 2022 at 10:35:19AM +0800, brookxu.cn@gmail.com wrote:
> We want to choose an LTS kernel version to use for a few years. As we know,
> the 5.10 LTS has a 6 years maintenance period with the help of huawei. But
> the 5.15 LTS currently only has a two-year maintenance period, and it may
> reach EOL next year. It is currently unclear whether it will be extended.

It all depends on what level of effort you're willing to make:

- if you really want to just use and not participate at all (i.e. report
  issues, test pre-releases etc), 5.10 will be more suited.

- if you're willing to participate, you can start to encourage others to
  do so as well in order to convince Greg that he will not be alone in
  this tedious task and that it's worth extending 5.15.

- or if you're willing to invest a little bit of time but don't want to
  engage too far, you could also take the risk of going for 5.15, hoping
  that it will be extended, knowing that if it's not, it will be your
  job to deal with backports (which usually is a real pain and would
  justify giving back some help on official support instead).

> Coupled with the arrival of the 6.0 kernel, I am a little worried that the
> maintenance of 5.15 will be reduced. Does anyone have good suggestions,
> thank you.

That's just numbering, and should in no way affect maintenance of existing
code.

Hoping this helps,
Willy

      reply	other threads:[~2022-08-08  3:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  2:35 brookxu.cn
2022-08-08  3:36 ` Willy Tarreau [this message]

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=20220808033643.GB7325@1wt.eu \
    --to=w@1wt.eu \
    --cc=brookxu.cn@gmail.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®