Hi,

Just checked out this new structure, will refresh & test and submit.
Where do you want the security patches? How do we deal with config
changes?


--
// Janne

On 12/21/2010 11:04 PM, ext Arjan van de Ven wrote:
Hi,

last week the TSG approved the new kernel policy, which, in short has
two aspects

1) MeeGo will have a reference kernel that is close to upstream, for all
platforms that have basically all the code they need
already in the upstream kernel. (give or take a few bugfixes)
2) Per platform kernels for those platforms that are not *yet* upstream,
and/or may not be able to run a current upstream kernel.

The architecture team picks a kernel version for each release, and while
this sounds very fancy... it's actually almost math...
For MeeGo 1.2, the choice is made for 2.6.37; 2.6.37 is just about
released and will be released before the January feature freeze date.

As such, I've updated the kernel in devel:kernel to match this new
policy, and will be submitting this to Trunk:Testing today.
The n900 adaptation team has a kernel in the works already for their
platform, as do various others.


_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel


_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel

Reply via email to