Yocto Project - User contributions [en]

Kernel/1.9 Planning

2015-05-22T19:18:25Z

Bruce.ashfield: /* 1.9 Priorities */

=1.9 Planning=

==1.9 Priorities==
* BSP Updates & Consolidation
** Update Linux Yocto
*** Verify SCC/CFG to remove duplication
*** Refactor intel-common & clean
*** LTSI update, -rt refresh, 3.14/3.19 removed
** Kernel Workflow
*** Streamline kernel configuration handling, remove meta data from kernel tree
*** Allow configuration fragments for any time of kernel, make linux-yocto a thin shim
** Kernel Packaging
*** Allow Multiple installed kernels, multi kernel build
** Remove deprecated BSPs
*** Sugarbay, Crownbay
*** FRI2, NUC, eMenlow
*** Crystalforest, Jasperforest
** Incorporate Quark Core BSP
** Investigate Silvermont as part of Core2
* Runtime BSP Customization
** Graphics
** Audio (HDMI Audio on NUC)
* Continue Poky Tiny
** Still needs to work
** Need to add tiny variant for Intel Core BSP
* Continue to improve Developer Workflow

==1.9 Commitments==

=1.9 Kernel Team Bugs=
==1.9 Bug Status by Milestone==
{{#bugzilla:
|group=milestone
|bar=status
|status=*
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9,1.9 M1,1.9 M2,1.9 M3,1.9 M4
}}

==1.9 Open Bug Priority by Milestone==
{{#bugzilla:
|group=milestone
|bar=priority
|status=!(RESOLVED,VERIFIED)
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9,1.9 M1,1.9 M2,1.9 M3,1.9 M4
}}

==1.9 Weekly Activity==
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9,1.9 M1,1.9 M2,1.9 M3,1.9 M4
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|modified=-1w
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

==1.9 Resolved Bugs==
{{#bugzilla:
|group=to
|status=RESOLVED
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9,1.9 M1,1.9 M2,1.9 M3,1.9 M4
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

==1.9 Targeted Bugs==
===1.9 M1===
====Completed Bugs====
{{#bugzilla:
|group=to
|status=RESOLVED,VERIFIED,CLOSED
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9 M1
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}
====Scheduled Bugs====
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9 M1
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===1.9 M2===
====Completed Bugs====
{{#bugzilla:
|group=to
|status=RESOLVED,VERIFIED,CLOSED
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9 M2
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}
====Scheduled Bugs====
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9 M2
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===1.9 M3===
====Completed Bugs====
{{#bugzilla:
|group=to
|status=RESOLVED,VERIFIED,CLOSED
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9 M3
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}
====Scheduled Bugs====
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9 M3
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===1.9 M4===
====Completed Bugs====
{{#bugzilla:
|group=to
|status=RESOLVED,VERIFIED,CLOSED
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9 M4
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}
====Scheduled Bugs====
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9 M4
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}
===1.9 Backlog===
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=1.9
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===Previous Backlog (!1.9,!Future)===
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=!(1.9,1.9 M1, 1.9 M2, 1.9 M3, 1.9 M4, 1.9 M5, Future)
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===Meta-Intel Backlog (!Future)===
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|component=bsps-meta-intel
|milestone=!(Future)
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===Previous Backlog===
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=!(1.9,1.9 M1, 1.9 M2, 1.9 M3, 1.9 M4, 1.9 M5, 1.9 M6, 1.8, Future)
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===Future===
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,bruce.ashfield@windriver.com,saul.wold@intel.com
|milestone=Future
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

=Previous Release 1.8 Info=

==1.8 Priorities==
* Developer Workflow
** Silent failure, CONFIG_ missing/overridden/irrelevant - Fixed
* Automation and QA Testing
** Kernel manual guides
*** Testing the process within the Manual
*** Tooling would change and process would break
*** This will need to be pushed to 1.9
* Meta-Data cleanup
** intel-common - factor our platforms, don't just include the entire BSP scc
* BSP Updates
* linux-yocto-dev by M1
* <strike>Deployment</strike> Mark Hatle owns this now
* BSP Refactor
** Not including whole BSPs
** purge remaining MACHINE_ARCH packages for meta-intel
** runtime BSP customization (aka HDMI audio on the NUC, etc.)
* Continue Poky Tiny
** Still needs to work
** Need to add tiny variant for Intel Core BSP
* Future
** Autobuilder detection of config changes

==1.8 Commitments==
* The MUT branch will be built using linux-yocto-dev on a regular basis on the Autobuilder starting at M1.
* The versioned kernel recipe will be submitted at RC1 and before feature-freeze.
* 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.

Kernel/1.7 Planning

2014-03-27T20:11:26Z

Bruce.ashfield: /* 1.7 Commitments */

=1.7 Planning=
==Next Actions==
* [ ] Submit versioned kernel recipe at RC1
* [ ] Provide QA tests to QA Team to include in their QA efforts
** recipe-space tooling
*** scc
*** cfg
*** defconfig
** linux-yocto-custom usage
** externalsrc
** no machine/meta branches

==1.7 Priorities==
* Developer Workflow
* Automation and QA Testing
* Meta-Data cleanup
* BSP Updates
* linux-yocto-dev by M1
* Deployment
* BSP Consolidation
* Continue Poky Tiny

==1.7 Commitments==
* The MUT branch will be built using linux-yocto-dev on a regular basis on the Autobuilder starting at M1.
* The versioned kernel recipe will be submitted at RC1 and before feature-freeze.
* The core-image-kernel-dev recipe will be moved from poky-extras into oe-core and used for kernel sanity and stress testing.
* 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.

=1.7 Kernel Team Bugs=
==1.7 Bug Status by Milestone==
{{#bugzilla:
|group=milestone
|bar=status
|status=*
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7,1.7 M1,1.7 M2,1.7 M3,1.7 M4,1.7 M5,1.7 M6
}}

==1.7 Open Bug Priority by Milestone==
{{#bugzilla:
|group=milestone
|bar=priority
|status=!(RESOLVED,VERIFIED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7,1.7 M1,1.7 M2,1.7 M3,1.7 M4,1.7 M5,1.7 M6
}}

==1.7 Weekly Activity==
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7,1.7 M1,1.7 M2,1.7 M3,1.7 M4,1.7 M5,1.7 M6
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|modified=-1w
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

==1.7 Resolved Bugs==
{{#bugzilla:
|group=to
|status=RESOLVED
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7,1.7 M1,1.7 M2,1.7 M3,1.7 M4,1.7 M5,1.7 M6
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

==1.7 Targeted Bugs==
===1.7 M1===
====Completed Bugs====
{{#bugzilla:
|group=to
|status=RESOLVED,VERIFIED,CLOSED
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7 M1
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}
====Scheduled Bugs====
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7 M1
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===1.7 M2===
====Completed Bugs====
{{#bugzilla:
|group=to
|status=RESOLVED,VERIFIED,CLOSED
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7 M2
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}
====Scheduled Bugs====
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7 M2
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===1.7 M3===
====Completed Bugs====
{{#bugzilla:
|group=to
|status=RESOLVED,VERIFIED,CLOSED
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7 M3
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}
====Scheduled Bugs====
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7 M3
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===1.7 M4===
====Completed Bugs====
{{#bugzilla:
|group=to
|status=RESOLVED,VERIFIED,CLOSED
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7 M4
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}
====Scheduled Bugs====
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7 M4
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===1.7 M5===
====Completed Bugs====
{{#bugzilla:
|group=to
|status=RESOLVED,VERIFIED,CLOSED
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7 M5
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}
====Scheduled Bugs====
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7 M5
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===1.7 Backlog===
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=1.7
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===Previous Backlog (!1.7,!Future)===
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=!(1.7,1.7 M1, 1.7 M2, 1.7 M3, 1.7 M4, 1.7 M5, 1.7 M6, 1.7, Future)
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===Meta-Intel Backlog (!Future)===
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|component=bsps-meta-intel
|milestone=!(Future)
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===Previous Backlog===
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=!(1.7,1.7 M1, 1.7 M2, 1.7 M3, 1.7 M4, 1.7 M5, 1.7 M6, 1.7, Future)
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

===Future===
{{#bugzilla:
|group=to
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
|milestone=Future
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|total=summary,estimated
|noresultsmessage="No matching bugs found."
}}

Yocto 1.1 Schedule

2011-03-31T16:51:48Z

Bruce.ashfield:

= October 2011 (release date: October 6, 2011) =
----
The detailed milestone map for the October 2011 release of Yocto is as below.

== pre-M1 (March 14 to April 18 -- Feature List and Schedule Defined April 18) ==
* Features Submitted to web - by April 1st
* Features prioritized and added to schedule - by April 12th

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Architecture || OE Core || Restructuring, renaming, rebranding || 1 || Review || Richard || Architect ||
|-
|| 1.0 Carryover || multi-lib || multi-lib support for 32-bit & 64-bit and capable of being installed at the same time || 1 || Review || Richard || 1.0 Carryover ||
|-
|| Meta-Data || OE Comparison || Compare Yocto core set against integration work in OE and other distributions looking for bug fixes, (relevant) feature enhancements, and integration/policy hints. || 1 || Accept || Mark || Meta-data ||
|-
|| BSPs || Support for AVX as in kernel 2.6.30. - Already in 1.0? || Any toolchain support needed? Is it already in GCC? Ensure part of toolchain update (if not already present). Verify with Bruce that AVX is enabled in kernel version XXX?
|| 1 || Accept || Saul / Nitin || Jay / ECG ||
|-
|| Misc || User creation at post-install || || 1 || Accept || Mark || Architect ||
|-
|| Build || Autobuilder maintenance || Bring scripts into configuration or get git repo working for those that can't be brought in. || 1 || Accept || Beth || Beth ||
|-
|| Build || License tracking || Get common licenses for all packages. (takes ~3 days) || 1 || Accept || Beth || Beth ||
|-
|| Overall || Process Improvement || Host a retrospective to discuss what went well and what can be improved in Yocto 1.0. || 1 || Accept || Beth || Beth ||
|-
|| Project || Release Readiness || Release Readiness Meeting || 1 || Jun-6 || Julie || Julie||
|-
|| Point Release || Build/Release/QA || We need a point release to fix bugs targeted for point release. || 1 || Accept || Beth/Yongkang|| Team||
|-
|| Performance || Plan for Performance || This is a placeholder to spend time this milestone determining the plan for improving performance. Various P1, P2, P3 tasks will be output as a result of this planning. || 1 || Review || Richard/Dongxiao || Team||
|-
|| Documentation || OOB documentation || Create an out of box guide for giveaway systems built using Yocto by EO May. || 1|| Review || ScottR || Julie ||
|-
|| kernel || kernel tools || refactor/clean the kernel tools for more general use. include the tools withing the kernel repo, not in a separate repo|| 1|| Review || Bruce || Bruce ||
|-
|| kernel || kernel build || auto yoctization. allow the building of arbitrary repos and kernel versions via the yocto kernel meta data|| 1|| Review || Bruce || Bruce ||
|-
|| kernel || kernel update ||kernel dev/next repo created. feature merges (fs, boot, tiny, controllers, etc). reference tree merges (omap, davinci, etc)|| 1|| Review || Bruce || Bruce ||
|-
|}

== M2 (May 30 to Jul 25 -- Design Complete Jun 6, Dev Complete Jul 4, Stabilize Complete Jul 18, Release Complete Jul 25) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| 1.0 Carryover || Image Creator || finish the Image Creator to add features pushed out from 1.0 || 1 || Accept || Joshua + Jessica || 1.0 Carryover ||
|-
|| Architecture || Layer Tooling || This includes the architectural work plus implementing the changes || 1 || Review || Richard || Architect ||
|-
|| Meta-data || Upstream our patches || Placeholder for time for the team to upstream patches || 1 || Accept || Saul || Meta-Data Team||
|-
|| Meta-data|| Error handling in bitbake || add additional error handling to bitbake (check bugzilla for existing error handling and warning bugs) || 1 || Accept || Saul || Architect ||
|-
|| ADT || Changes for Image Creator || Eclipse changes pending Image Creator || 1 || Review || Jessica || ADT Team||
|-
|| BSP || Tutorials || Create tutorials and documentation on how to create a BSP || 1 || Accept || Tom, Scott || Team||
|-
|| Kernel|| Fast Boot Time || 2 second boot time target || 1 || Accept || Darren|| Team ||
|-
|| Build || Meta-Targets || Part of the challenge of autobuilder is that you have to go into autobuilder, edit script, reconfigure, to change just one build target. This is error prone. What we need is a meta-target where Beth can say she wants to build Poky-image-sato for QEMU x86 and have it just do that. Beth thinks this is done via an override to the web page. (takes ~2 weeks) || 1 || Accept || Beth || Beth||
|-
|| Build || License tracking || Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks) || 1 || Accept || Beth || Beth||
|-
|| Build || Autobuilder Infrastructure || Bring up additional autobuilders and work with sysadmin to configure. || 1 || Accept || Beth || Beth||
|-
|| Misc || adding eglibc config control || this goes with the package config options || 1.5 || Accept || Mark || Architect ||
|-
|| Misc || Directory Ownership || || 1.5 || Accept || Mark || Architect || a bit concerned this will take longer then expected
|-
|| Project || Release Readiness || Release Readiness Meeting || 1 || Jul-18 || Julie || Julie||
|-
|| BSPs || BSP update/intro ||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)|| 2|| Review || Bruce/Richard/team || Bruce ||
|-
|| kernel || BSP config cleanup||BSP config cleanup/refactoring. Update to new kernel rev. Investigate Kconfig alignment|| 1|| Review || Bruce|| Bruce ||
|-
|| kernel || inter-core comms||investigate/report/merge intercore communication methods (mcapi, dsplink,etc). extend as appropriate|| 2|| Review || Bruce|| Bruce ||

|}

== M3 (Jul 11 to Aug 15 -- Design Complete Jul 18, Dev Complete Jul 25, Stabilize Complete Aug 8, Release Complete Aug 15) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Build || Release Scripts || Create Release Scripts for OCT 2011 release || 1 || Review || Beth || Beth ||
|-
|| Project || Release Readiness || Release Readiness Meeting || 1 || Aug-8 || Julie || Julie||
|-
|| Alpha || Alpha Program || Participants determined - Aug 1; Program - Aug 8-22; Feedback available - Aug 25 || 1 ||Accept || Julie || Julie||
|-
|| kernel || usecases|| BSP config streamlining, building the kernel standalone, yoctoization, meta data sharing || 1 ||Review || Bruce|| Bruce||
|}

== M4 (Aug 15 to Oct 6 -- Stabilize Complete Aug 29, Release Complete Oct 3) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Project || Release Candidate 1 || RC1 generated || 1 || Aug-29|| Beth || Team ||
|-
|| Project || Release Candidate 2 || RC2 generated || 1 || Sep-5|| Beth || Team ||
|-
|| Project || Release Candidate 3 || RC3 generated || 1 || Sep-12|| Beth || Team ||
|-
|| Project || Release Candidate 4 || RC4 generated || 1 || Sep-19|| Beth || Team ||
|-
|| Project || Release Readiness || Release Readiness Meeting || 1 || Sep-26 || Julie || Julie||
|-
|| QA || Holiday || QA team on holiday Oct 1 - 7 || 1 || Oct 1-7 || QA || QA ||
|}

Yocto 1.1 Schedule

2011-03-31T16:46:34Z

Bruce.ashfield:

= October 2011 (release date: October 6, 2011) =
----
The detailed milestone map for the October 2011 release of Yocto is as below.

== pre-M1 (March 14 to April 18 -- Feature List and Schedule Defined April 18) ==
* Features Submitted to web - by April 1st
* Features prioritized and added to schedule - by April 12th

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Architecture || OE Core || Restructuring, renaming, rebranding || 1 || Review || Richard || Architect ||
|-
|| 1.0 Carryover || multi-lib || multi-lib support for 32-bit & 64-bit and capable of being installed at the same time || 1 || Review || Richard || 1.0 Carryover ||
|-
|| Meta-Data || OE Comparison || Compare Yocto core set against integration work in OE and other distributions looking for bug fixes, (relevant) feature enhancements, and integration/policy hints. || 1 || Accept || Mark || Meta-data ||
|-
|| BSPs || Support for AVX as in kernel 2.6.30. - Already in 1.0? || Any toolchain support needed? Is it already in GCC? Ensure part of toolchain update (if not already present). Verify with Bruce that AVX is enabled in kernel version XXX?
|| 1 || Accept || Saul / Nitin || Jay / ECG ||
|-
|| Misc || User creation at post-install || || 1 || Accept || Mark || Architect ||
|-
|| Build || Autobuilder maintenance || Bring scripts into configuration or get git repo working for those that can't be brought in. || 1 || Accept || Beth || Beth ||
|-
|| Build || License tracking || Get common licenses for all packages. (takes ~3 days) || 1 || Accept || Beth || Beth ||
|-
|| Overall || Process Improvement || Host a retrospective to discuss what went well and what can be improved in Yocto 1.0. || 1 || Accept || Beth || Beth ||
|-
|| Project || Release Readiness || Release Readiness Meeting || 1 || Jun-6 || Julie || Julie||
|-
|| Point Release || Build/Release/QA || We need a point release to fix bugs targeted for point release. || 1 || Accept || Beth/Yongkang|| Team||
|-
|| Performance || Plan for Performance || This is a placeholder to spend time this milestone determining the plan for improving performance. Various P1, P2, P3 tasks will be output as a result of this planning. || 1 || Review || Richard/Dongxiao || Team||
|-
|| Documentation || OOB documentation || Create an out of box guide for giveaway systems built using Yocto by EO May. || 1|| Review || ScottR || Julie ||
|-
|| kernel || kernel tools || refactor/clean the kernel tools for more general use. include the tools withing the kernel repo, not in a separate repo|| 1|| Review || Bruce || Bruce ||
|-
|| kernel || kernel build || auto yoctization. allow the building of arbitrary repos and kernel versions via the yocto kernel meta data|| 1|| Review || Bruce || Bruce ||
|-
|| kernel || kernel update ||kernel dev/next repo created. feature merges (fs, boot, tiny, controllers, etc). reference tree merges (omap, davinci, etc)|| 1|| Review || Bruce || Bruce ||
|-
|}

== M2 (May 30 to Jul 25 -- Design Complete Jun 6, Dev Complete Jul 4, Stabilize Complete Jul 18, Release Complete Jul 25) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| 1.0 Carryover || Image Creator || finish the Image Creator to add features pushed out from 1.0 || 1 || Accept || Joshua + Jessica || 1.0 Carryover ||
|-
|| Architecture || Layer Tooling || This includes the architectural work plus implementing the changes || 1 || Review || Richard || Architect ||
|-
|| Meta-data || Upstream our patches || Placeholder for time for the team to upstream patches || 1 || Accept || Saul || Meta-Data Team||
|-
|| Meta-data|| Error handling in bitbake || add additional error handling to bitbake (check bugzilla for existing error handling and warning bugs) || 1 || Accept || Saul || Architect ||
|-
|| ADT || Changes for Image Creator || Eclipse changes pending Image Creator || 1 || Review || Jessica || ADT Team||
|-
|| BSP || Tutorials || Create tutorials and documentation on how to create a BSP || 1 || Accept || Tom, Scott || Team||
|-
|| Kernel|| Fast Boot Time || 2 second boot time target || 1 || Accept || Darren|| Team ||
|-
|| Build || Meta-Targets || Part of the challenge of autobuilder is that you have to go into autobuilder, edit script, reconfigure, to change just one build target. This is error prone. What we need is a meta-target where Beth can say she wants to build Poky-image-sato for QEMU x86 and have it just do that. Beth thinks this is done via an override to the web page. (takes ~2 weeks) || 1 || Accept || Beth || Beth||
|-
|| Build || License tracking || Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks) || 1 || Accept || Beth || Beth||
|-
|| Build || Autobuilder Infrastructure || Bring up additional autobuilders and work with sysadmin to configure. || 1 || Accept || Beth || Beth||
|-
|| Misc || adding eglibc config control || this goes with the package config options || 1.5 || Accept || Mark || Architect ||
|-
|| Misc || Directory Ownership || || 1.5 || Accept || Mark || Architect || a bit concerned this will take longer then expected
|-
|| Project || Release Readiness || Release Readiness Meeting || 1 || Jul-18 || Julie || Julie||
|}

== M3 (Jul 11 to Aug 15 -- Design Complete Jul 18, Dev Complete Jul 25, Stabilize Complete Aug 8, Release Complete Aug 15) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Build || Release Scripts || Create Release Scripts for OCT 2011 release || 1 || Review || Beth || Beth ||
|-
|| Project || Release Readiness || Release Readiness Meeting || 1 || Aug-8 || Julie || Julie||
|-
|| Alpha || Alpha Program || Participants determined - Aug 1; Program - Aug 8-22; Feedback available - Aug 25 || 1 ||Accept || Julie || Julie||
|}

== M4 (Aug 15 to Oct 6 -- Stabilize Complete Aug 29, Release Complete Oct 3) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Project || Release Candidate 1 || RC1 generated || 1 || Aug-29|| Beth || Team ||
|-
|| Project || Release Candidate 2 || RC2 generated || 1 || Sep-5|| Beth || Team ||
|-
|| Project || Release Candidate 3 || RC3 generated || 1 || Sep-12|| Beth || Team ||
|-
|| Project || Release Candidate 4 || RC4 generated || 1 || Sep-19|| Beth || Team ||
|-
|| Project || Release Readiness || Release Readiness Meeting || 1 || Sep-26 || Julie || Julie||
|-
|| QA || Holiday || QA team on holiday Oct 1 - 7 || 1 || Oct 1-7 || QA || QA ||
|}