On Mon, Jan 27, 2014 at 3:50 AM, Dominig ar Foll (Intel OTC) <
[email protected]> wrote:

> Hello,
>
> I see in that some of us would like to integrate very early features in
> Tizen Kernel while some other would prefer to remain conservative.
> In order to agree on a common model, I would like to propose the following
> simple concepts.
>
>  - Only patches accepted in a published 'release' Linux Kernel can be used
> in Tizen Base/Common
>  - Kernel source should be common for all verticals, but Kernel config is
> vertical specific.
>  - Tizen Generic (which is only a development tool) will follow that rule.
>  - Back-ported patches accepted in a more recent 'release' of the kernel
> are acceptable in Tizen Base/Common
>  - Vertical may decide to use non "released" patches but that is not
> advisable.
>  - Platform integrator remain free of their implementation as long as it
> complies with their vertical requirements.
>
>
> That model should allow us to remain agile, while protecting us to
> introduce fork from the kernel main line and to create a maintenance
> nightmare.
>
> Feedback is welcome.
>
> --
> Dominig ar Foll
> Senior Software Architect
> Open Source Technology Centre
> Intel SSG
>
> _______________________________________________
> Dev mailing list
> [email protected]
> https://lists.tizen.org/listinfo/dev
>

Has the LTSI kernel, which is maintained by Greg Kroah-Hartman, been
considered?

This is very similar to the use case that motivated the creation of the
Long Term Support Initiative, to provide a kernel version that is stable
and fit for products, while still receiving select backports from newer
mainline releases.  The longer cycle time between major kernel versions
(one year, vs. every 2.5 months) is intended to make it easier to choose a
single kernel version to converge upon, particularly when there are
multiple companies or products involved.

http://ltsi.linuxfoundation.org/what-is-ltsi

Best,
Brian
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to