|
|
| Line 1: |
Line 1: |
| = Yocto Project 1.1 (release date: October 6, 2011) =
| |
| ----
| |
| The detailed milestone map for the 1.1 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 (Qing) || 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 pre-install || || 1 || Accept || Mark (ScottG) || Architect ||
| |
| |-
| |
| || Build || Autobuilder maintenance || Bring scripts into configuration or get git repo working for those that can't be brought in. (~1.5 weeks)|| 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. (Beths end: ~1-2 days of work with PRC. Release is trivial.)|| 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 ||
| |
| |-
| |
| || QA || Overall Test Plan || Create an overall Test Plan with details on Strategy, Approach, Types of Testing, Features included and not included, Hardware needed, Schedule, and Resources and publish to Wiki || 1|| Accept - May 6|| Jiajun|| Jiajun||
| |
| |-
| |
| || QA || Test Execution Plan || Create a Test Execution Plan with specific Test Cases || 1|| Accept - May 16 || Jiajun|| Jiajun||
| |
| |}
| |
|
| |
| == 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 (ScottG) || 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. (2 days per machine for OS. 1 hour for ab setup)|| 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 (Qing) || 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 ||
| |
| |-
| |
| || QA || Test Execution Plan || Create a Test Execution Plan with specific Test Cases || 1|| Accept - June 27 || Jiajun|| Jiajun||
| |
|
| |
| |}
| |
|
| |
| == 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 (one week)|| 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||
| |
| |-
| |
| || QA || Test Execution Plan || Create a Test Execution Plan with specific Test Cases || 1|| Accept - Jul 18 || Jiajun|| Jiajun||
| |
| |}
| |
|
| |
| == 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 ||
| |
| |}
| |
