public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Tyler Hicks (Microsoft)" <code@tyhicks.com>
Cc: Suleiman Souhlal <suleiman@google.com>,
	sashal@kernel.org, Sangwhan Moon <sxm@google.com>,
	stable@vger.kernel.org,
	Kelsey Steele <kelseysteele@linux.microsoft.com>,
	Allen Pais <stable.kernel.dev@gmail.com>
Subject: Re: LTS 5.15 EOL Date
Date: Thu, 10 Nov 2022 09:22:08 +0100	[thread overview]
Message-ID: <Y2y0sOGT4UrKj6JV@kroah.com> (raw)
In-Reply-To: <20221109234526.r5raofrnzddggarw@sequoia>

On Wed, Nov 09, 2022 at 05:45:26PM -0600, Tyler Hicks (Microsoft) wrote:
> On 2022-10-29 08:28:55, gregkh@linuxfoundation.org wrote:
> > On Fri, Oct 28, 2022 at 02:40:19PM -0500, Tyler Hicks (Microsoft) wrote:
> > > On 2022-10-20 10:26:06, gregkh@linuxfoundation.org wrote:
> > > > On Thu, Oct 20, 2022 at 08:25:35AM +0900, Suleiman Souhlal wrote:
> > > > > Hello,
> > > > > 
> > > > > I saw that the projected EOL of LTS 5.15 is Oct 2023.
> > > > > How likely is it that the date will be extended? I'm guessing it's
> > > > > pretty likely, given that Android uses it.
> > > > 
> > > > Android is the only user that has talked to me about this kernel
> > > > version so far.  Please see:
> > > > 	http://kroah.com/log/blog/2021/02/03/helping-out-with-lts-kernel-releases/
> > > > for what I require in order to keep an LTS kernel going longer than 2
> > > > years.
> > > 
> > > Microsoft is also interested in a longer lifetime for v5.15 LTS. An
> > > additional year should meet our needs.
> > 
> > Wonderful, thanks for letting us know.
> > 
> > > We are aware of your "Helping Out ..." blog post and have been making
> > > improvements to be of more assistance. Kelsey and Allen (Cc'ed) have
> > > been doing -rc testing of v5.15 -rc releases and reporting the results
> > > to the list, on behalf of Microsoft. Testing of the -rc releases is
> > > mostly manual at this point, so we don't get every release tested before
> > > the release happens, but we're working on improving our processes and
> > > having builds/tests kick off automatically so that you can rely on us
> > > even more. We should have a much better system in place to help with
> > > testing and reporting by the time Oct 2023 rolls around. :)
> > 
> > Don't you all use kernelci already?  Doesn't that fit into your testing
> > environment already to make this easier?
> 
> You're right that we provide kernelci resources for the broader
> community but we use something different internally.
> 
> > 
> > And yes, I have seen the testing results, thank you for that.  If you
> > all want to be added to the initial -rc1 email announcement to help
> > trigger any build systems that way, just let me know.
> 
> Thanks. I had planned to watch for new pushes to the linux-stable-rc.git
> branches. If that doesn't work for some reason, we'll take you up on the
> email offer.

Watch out when using that tree, it is rebased all the time and contains
intermediate steps before the "real" -rc releases happen.  It is there
for systems that can not handle quilt series.

good luck!

greg k-h

      reply	other threads:[~2022-11-10  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 23:25 LTS 5.15 EOL Date Suleiman Souhlal
2022-10-20  8:26 ` gregkh
2022-10-25  0:58   ` Suleiman Souhlal
2022-10-28 19:40   ` Tyler Hicks (Microsoft)
2022-10-29  6:28     ` gregkh
2022-11-09 23:45       ` Tyler Hicks (Microsoft)
2022-11-10  8:22         ` gregkh [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=Y2y0sOGT4UrKj6JV@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=code@tyhicks.com \
    --cc=kelseysteele@linux.microsoft.com \
    --cc=sashal@kernel.org \
    --cc=stable.kernel.dev@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=suleiman@google.com \
    --cc=sxm@google.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