stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mason <slash.tmp@free.fr>
Cc: stable@vger.kernel.org
Subject: Re: Status of v4.9
Date: Mon, 16 Jan 2017 15:29:24 +0100	[thread overview]
Message-ID: <20170116142924.GA28940@kroah.com> (raw)
In-Reply-To: <a7813639-b147-b524-e29c-93f459687374@free.fr>

On Mon, Jan 16, 2017 at 03:11:58PM +0100, Mason wrote:
> On 16/01/2017 14:02, Greg Kroah-Hartman wrote:
> 
> > On Mon, Jan 16, 2017 at 01:35:38PM +0100, Mason wrote:
> >
> >> On 16/01/2017 11:34, Greg Kroah-Hartman wrote:
> >>
> >>> On Mon, Jan 16, 2017 at 09:39:39AM +0100, Mason wrote:
> >>>
> >>>> Hello Greg,
> >>>>
> >>>> A few months ago, you stated that you were considering making v4.9
> >>>> the latest LTS version.
> >>>>
> >>>> http://kroah.com/log/blog/2016/09/06/4-dot-9-equals-equals-next-lts-kernel/
> >>>>
> >>>> Neither https://www.kernel.org/ nor https://www.kernel.org/category/releases.html
> >>>> list 4.9 as an LTS version yet.
> >>>>
> >>>> Could you clear (some of) my confusion?
> >>>
> >>> It's a bit hard for a kernel to be "LTS" when it hasn't even had the
> >>> chance to move out of the "normal" stable release process, right? :)
> >>
> >> I think it might be worthwhile mentioning somewhere that 4.9 is LTS.
> >> (My manager thought 4.4 was the latest.)
> > 
> > As you can see by my questions, I haven't come to that final conclusion
> > yet :)
> 
> Sorry, I must be missing something obvious :-)
> 
> What are the advantages of not listing 4.9 in the LTS list(*)
> until 4.11 is released?
> 
> (*) https://www.kernel.org/category/releases.html

It gives me the chance to not make 4.9 a LTS kernel if something shows
up that is a really big problem.  People have only been really testing
4.9 for a few weeks (really only 2 given the holidays.)  Let's see what
shakes out first, ok?

Has anyone run any benchmarks yet even?  Have you?

What is the advantage of me listing it now?  Is that going to cause
anyone to do any extra work today for helping to test this out that it
wouldn't have?

If you need to point a manager at something, point them at my blog post,
that is why I wrote it.  And test the heck out of it starting now!

thanks,

greg k-h

  reply	other threads:[~2017-01-16 14:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16  8:39 Status of v4.9 Mason
2017-01-16 10:34 ` Greg Kroah-Hartman
2017-01-16 12:35   ` Mason
2017-01-16 13:02     ` Greg Kroah-Hartman
2017-01-16 14:11       ` Mason
2017-01-16 14:29         ` Greg Kroah-Hartman [this message]
2017-01-16 14:39           ` Willy Tarreau
2017-01-16 15:55             ` Greg Kroah-Hartman
2017-01-16 17:42               ` Willy Tarreau
2017-01-16 18:34                 ` Willy Tarreau
2017-01-17  7:15                   ` Greg Kroah-Hartman
2017-01-17  7:28                     ` Willy Tarreau
2017-01-17  7:45           ` Christoph Biedl
2017-06-05 21:41             ` Christoph Biedl
2017-01-17  9:15       ` Mason

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=20170116142924.GA28940@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=slash.tmp@free.fr \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).