mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
	helpdesk@kernel.org, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Michael Larabel <Michael@michaellarabel.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Please, clear statement to what is next LTS linux-kernel
Date: Wed, 11 Jan 2023 06:11:13 +0100	[thread overview]
Message-ID: <Y75E8Y7FPGjxL0xx@kroah.com> (raw)
In-Reply-To: <CA+icZUUYrasObBwMQWae=+eAfUzvxc1Pk39QFz9=NXedWO41Vg@mail.gmail.com>

On Tue, Jan 10, 2023 at 09:22:48PM +0100, Sedat Dilek wrote:
> Happy new 2023,
> 
> I normally watch [1] for the next LTS linux-kernel which is for me an
> official site and for an official announcement.
> 
> On the debian-kernel mailing list you read Linux 6.1 will be the
> official one for Debian-12 aka bookworm.
> 
> I saw a phoronix article about EOL of Linux-4.9 [3] which points to [2].
> 
> [2] says:
> 
> After being prompted on the kernel mailing list, Linux stable
> maintainer Greg Kroah-Hartman commented:
> > I usually pick the "last kernel of the year", and based on the normal release cycle, yes, 6.1 will be that kernel.
> > But I can't promise anything until it is released, for obvious reasons.
> 
> This is not a clear statement for me and was maybe at a point where
> 6.1 was not released.
> 
> If you published a clear statement please point me to it.
> And if so, please update [1] accordingly.
> ( It dropped 4.9 from LTS list recently from [1] - guess Konstantin or
> someone from helpdesk did - so [1] is actively maintained. )
> 
> Please, a clear statement.

Why exactly do you need a "clear statement"?  What will that change (or
not change) if it is made?

Please see this previous thread for what I need from others before I can
make such a thing:
	https://lore.kernel.org/r/Y53BputYK+3djDME@kroah.com

Can you help answer those questions for your use case please?  That will
help us make our decision.

thanks,

greg k-h

  parent reply	other threads:[~2023-01-11  5:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 20:22 Sedat Dilek
2023-01-10 20:28 ` Konstantin Ryabitsev
2023-01-11  5:11 ` Greg Kroah-Hartman [this message]
2023-01-11 19:28   ` Sedat Dilek

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=Y75E8Y7FPGjxL0xx@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Michael@michaellarabel.com \
    --cc=helpdesk@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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®