From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Next CIP kernel: CIP - Debian alignment
Date: Tue, 07 Nov 2017 17:21:48 +0000 [thread overview]
Message-ID: <1510075308.2465.28.camel@codethink.co.uk> (raw)
In-Reply-To: <5A01E24F.506@codethink.co.uk>
On Tue, 2017-11-07 at 17:41 +0100, Agustin Benito Bethencourt wrote:
> Hi Ben,
>
> one of the recurrent questions at ELCE, that also was done at the TSC?
> meeting is when will we pick the following kernel. The following?
> variables apply to this decision:
>
> * Some time ago, you made clear that, in order to keep the maintenance?
> effort affordable, we should not pick kernels in tight cadence. TSC?
> agreed to assume that advice.
>
> * Since we have agreed to base CIP-Core in Debian sources and during?
> ELCE 2017 we picked Debian as the default distro for CIP, it seems a?
> natural choice to pick LTS kernels that are also selected by Debian as?
> preferred choice.
>
> Based on your understanding about the Debian project:
>
> - When do you expect the next Debian kernel to be selected?
I take it that you mean the kernel for the next Debian stable release
(10/buster).
Debian is aiming to release roughly every 2 years. The last freeze was
delayed at my request, to allow inclusion of the LTS kernel selected at
the end of 2016, which was 4.9. So I would expect that the next Debian
release will include the LTS kernel selected at the end of 2018.
> - Based on that answer, which ones are the best candidates?
The kernel release cycle is 9-10 weeks, so I would expect the 2018 LTS
kernel to be 4.19 or 4.20/5.0. (I think I heard Linus say 4.19 will be
followed by 5.0, the same way 3.19 was followed by 4.0.)
> - Do you expect LTS and Debian selection to be aligned?
Absolutely.
> - If not, if this something you would like to see happening?
> - If yes, how can CIP help to make it happen?
I don't think CIP needs to do anything to encourage this.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
prev parent reply other threads:[~2017-11-07 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 16:41 [cip-dev] Next CIP kernel: CIP - Debian alignment Agustin Benito Bethencourt
2017-11-07 17:21 ` Ben Hutchings [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=1510075308.2465.28.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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.