Kernel/1.6 Planning

=1.6 Planning=
==Next Actions==
[x] Agree on terms by September 13 (everyone on To/Cc here needs to sign off, see below)
[ ] Saul to prepare MUT patch to set PREFERRED_PROVIDER to linux-yocto-dev (pending linux-yocto-dev as default kernel, needed for poky and meta-intel)
[x] Bruce to work with Saul to prepare mechanism for generating this patch (PREFERRED_PROVIDE and SRCREV updates for all layers - poky, yocto-bsp, meta-intel)
[x] Addressed backlog
[x] Darren: Open bugs for kernel team commitments for 1.6 (kernel test image, linux-yocto-dev srcrevs, etc)
* Expect large numbers of kernel related bugs in M2
[ ] Bruce: Open bug for linux-yocto-dev M1 (oe-core/yocto-bsps)
[x] All: Size your bugs after this call (just Darren is a slacker)
[ ] Darren: Get more of his urgent work into BZ
[x] Nitin: Open bug for M1 to move meta-intel BSPs to linux-yocto-dev
[ ] Darren: Talk to dave about any LTSI testing commitments
[x] Nitin: Communicate linux-yocto-dev process to ISG (part of larger meta-intel process documentation effort)
==1.6 Priorities==
* Automation and QA Testing
* Meta-Data cleanup
* BSP Hardware Refresh
* BSP Updates
* To linux-yocto-dev by M1
* Deployment
* BSP Variant
* BSP Consolidation
* Continue Poky Tiny
* Minnow2
==1.6 Commitments==
The 3.10 merge caused more churn and surprise breakage than was
considered acceptable 2 days prior to the feature freeze. Despite being
fixed very quickly, this disrupted a number of projects and we need to
mitigate this. We have committed to the following for the 1.6 development cycle.
* The MUT branch will be built using linux-yocto-dev on a regular basis on the Autobuilder starting as soon as possible into the development cycle of 1.6. This alone would have caught all the issues we encountered this time with ample time to resolve the issues prior to feature freeze. To ensure determinism, it is preferable to use fixed SRCREVs on the Autobuilder MUT builds over AUTOREV. Bruce and Saul need to iron out a workable mechanism to autogenerate a patch which sets a known good set of SRCREVs for the subsequent MUT build.
* The kernel team will create a core-image-kerneldev image for their regular development and testing which includes all known kernel-dependent packages, such as lttng-modules and hello-mod. More packages will be added as they are determined to be highly sensitive to kernel version.
* Two weeks prior to the feature freeze date, the kernel team will send a Kernel Status Report detailing the current state of linux-yocto-dev, including the most likely kernel version (98% confidence) based on the known inputs and enumerate any unknowns. The report will include a list of known issues from the MUT builds which will reduce the surprise and scramble following the merge. The issue list is expected to be minimal given the prior runs in MUT. Factors influencing the final linux-yocto kernel version include the base kernel version for PREEMPT_RT, LTSI, stable, etc. which are beyond our control. Depending on the priorities for the release, any of these may impact the final kernel version decision. Should new or late arriving information necessitate a change to the kernel version, it will be raised with the CCB and re will need to weigh the risk (which will be much less with the MUT builds) and possible schedule slippage with the benefits (such as aligning with LTSI or PREEMPT_RT). Note that we cannot always meet all requirements of schedule and external tree support and at each release we must choose between them.
=== linux-yocto-dev ===
* Cannot parse AUTOREV out of the box
* linux-yocto-dev recipe has anon python to prevent AUTOREV unless linux-yocto-dev is the preferred provider
* linux-yocto-dev will use fixed SRCREV recipe-kernel/linux/linux-yocto-dev-revisions.inc if it exists in the layer root, which will override AUTOREV when linux-yocto-dev is the PREFERRED_PROVIDER
* meta-intel CANNOT specifiy linux-yocto-dev as the PREFERRED_PROVIDER (unless we have that file, which we shouldn't as we want people to build with AUTOREV when they select PREFERRED_PROVIDER).
* meta-intel developers should specify PREFERRED_PROVIDER
=1.6 Kernel Team Bugs=
==1.6 Bug Status by Milestone==
==1.6 Open Bug Priority by Milestone==
==1.6 Weekly Activity==
==1.6 Resolved Bugs==
==1.6 Targeted Bugs==
===1.6 M1===
====Completed Bugs====
====Scheduled Bugs====
===1.6 M2===
====Completed Bugs====
====Scheduled Bugs====
===1.6 M3===
====Completed Bugs====
====Scheduled Bugs====
===1.6 M4===
====Completed Bugs====
====Scheduled Bugs====
===1.6 M5===
====Completed Bugs====
====Scheduled Bugs====
===1.6 Backlog===
===Previous Backlog (!1.6,!Future)===
===Meta-Intel Backlog (!Future)===
===Previous Backlog===
===Future===