All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: what's the next LTSI kernel version for long-term support
Date: Mon, 25 Feb 2013 19:35:24 -0800	[thread overview]
Message-ID: <20130226033524.GA25067@kroah.com> (raw)
In-Reply-To: <CAGsJ_4yxQK05hHUivYEnLD9=cAE4t5jNV7+6KJGu+LsVsSk1oQ@mail.gmail.com>

On Tue, Feb 26, 2013 at 11:06:56AM +0800, Barry Song wrote:
> Hi Greg/All,
> we have seen 3.4 was announced to be an LTSI in Aug, 2012. I'd like to
> know what is the next LTSI version since we might want to align our
> next release with LTSI.

Who is "we" here?

> That might help us to plan the release cycle.

As I've stated before, I do not announce the long-term kernel ahead of
time, we did that once in the past and it was a total mess.  I announce
it _after_ the kernel is released.

I have also stated that 3.8 is NOT going to be a long-term kernel, that
would mean I would be handling 3 long-term kernels at once, plus 1-2
"normal" stable kernels.  That is a sure way to drive me crazy and burn
out.

> BTW, how many people and SoC vendors in ARM communicaty want to align
> your releases with LTSI?

I do not know.  There was an LTSI meeting last week at ELC where this
was discussed, I suggest you ask the people who attended it. I was
there, but it's not up to me to release the meeting minutes, and I
wasn't taking notes, sorry.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Barry Song <21cnbao@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org,
	LKML <linux-kernel@vger.kernel.org>,
	Binghua Duan <Binghua.Duan@csr.com>
Subject: Re: what's the next LTSI kernel version for long-term support
Date: Mon, 25 Feb 2013 19:35:24 -0800	[thread overview]
Message-ID: <20130226033524.GA25067@kroah.com> (raw)
In-Reply-To: <CAGsJ_4yxQK05hHUivYEnLD9=cAE4t5jNV7+6KJGu+LsVsSk1oQ@mail.gmail.com>

On Tue, Feb 26, 2013 at 11:06:56AM +0800, Barry Song wrote:
> Hi Greg/All,
> we have seen 3.4 was announced to be an LTSI in Aug, 2012. I'd like to
> know what is the next LTSI version since we might want to align our
> next release with LTSI.

Who is "we" here?

> That might help us to plan the release cycle.

As I've stated before, I do not announce the long-term kernel ahead of
time, we did that once in the past and it was a total mess.  I announce
it _after_ the kernel is released.

I have also stated that 3.8 is NOT going to be a long-term kernel, that
would mean I would be handling 3 long-term kernels at once, plus 1-2
"normal" stable kernels.  That is a sure way to drive me crazy and burn
out.

> BTW, how many people and SoC vendors in ARM communicaty want to align
> your releases with LTSI?

I do not know.  There was an LTSI meeting last week at ELC where this
was discussed, I suggest you ask the people who attended it. I was
there, but it's not up to me to release the meeting minutes, and I
wasn't taking notes, sorry.

thanks,

greg k-h

  reply	other threads:[~2013-02-26  3:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26  3:06 what's the next LTSI kernel version for long-term support Barry Song
2013-02-26  3:06 ` Barry Song
2013-02-26  3:35 ` Greg Kroah-Hartman [this message]
2013-02-26  3:35   ` Greg Kroah-Hartman
2013-02-26  3:46   ` Barry Song
2013-02-26  3:46     ` Barry Song
2013-02-26  3:55     ` Greg Kroah-Hartman
2013-02-26  3:55       ` Greg Kroah-Hartman
2013-02-26  5:36       ` Barry Song
2013-02-26  5:36         ` Barry Song
2013-02-26  6:21         ` Greg Kroah-Hartman
2013-02-26  6:21           ` Greg Kroah-Hartman

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=20130226033524.GA25067@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.