View source for DarrenHart/Yocto 1.0 Schedule Formatting

= v1.0 (release date: Apr 15, 2011) =
----
The detailed milestone map for v1.0 is as below.  During the first week of each subsequent milestone past M1 we will have a demonstration of the previous milestone capabilities as well as a planning and design session for the current milestone.<br><br>

{|border="1" cellspacing="0"
|- style="background-color:#CCCCCC;"
|| '''Legend''' || '''Description'''
|- style="background-color:#CCCCCC;"
|| Completed || All items have been completed
|- style="background-color:green;"
|| On Track || All open items have future completion dates and are on track
|- style="background-color:yellow;"
|| At Risk || All open items have future completion dates, but some are at risk for missing them
|- style="background-color:red;"
|| Overdue || One or more items is overdue, action needed to get back On Track
|}

== M2 (Nov 08 to Dec 24 -- Dev Complete Dec 10, Stabilize Complete Dec 17, Release Complete Dec 24) ==
=== Sprint A (closes Nov 12, 11:59pm PDT -- pull request sent, initially reviewed) ===

{|border="1" cellspacing="0"
|- style="background-color:#CCCCCC"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links''' 
|-
|| Poky Features || Kernel interactive targets || To support incremental kernel development having the ability to run menuconfig (or xconfig, etc) directly is a common request. We'll need to add this for commercialization anyway. i.e. bitbake -c menuconfig. This fuctionality already exists. || 1 || Completed || Richard || bruceashfield || Enhancement 
|-
|| Distribution / components || Distro Audit: Upgrades Planned (Phase 1) || Complete plan for package upgrades in M2 || 1 || Done || Saul || || Continual Maintenance
|-
|| Validation || Runtime testing || Runtime testing of images as part of the autobuilder || 1 || Done || Jiajun/ScottG || rpurdie || project commitment
|- 
|| || Poky Image Creator Wireframe/Interaction Plans Complete ||  || 1 || Done || Josh || ||
|-
|| || SDK Generator Interaction: Plans Complete || || 1 || Done || Jessica || ||
|-
|| || Tracing/Profiling Planning Complete || This needs to cover where we're at now, what we're missing and also propose the future enhancements that may be needed. M2 targets getting existing tools integrated and documented. F2f discussion n the future enhancements || || Done || Tom || ||
|-
|| || Swabber. (Still needs to be integrated into weekly build by default) || || 1 || Done || Josh || ||
|-
|| Build/Release || Release process documentation || || || Done || Beth || ||
|-
|| Validation || Test plan for v1.0 (to address any deficiencies in coverage from v0.9)|| || 1 || Done || Jiajun || ||
|}

=== Sprint B (closes Nov 19, 11:59pm PDT -- pull request sent, initially reviewed) ===

{|border="1" cellspacing="0"
|- style="background-color:yellow"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Distribution / components|| Distro Audit: World Packages|| Audit world packages making sure it all build, making sure all are packages are required || 2|| Done || Saul|| sgw|| Hygiene
|-
|| Distribution / components|| Distro Audit: Package Description/Summary completed|| Ensure DESCRIPTION/SUMMARY fields are all audited|| 2|| WIP, Done by Dec 08|| Mark|| Mark|| Hygiene
|-
|| Tool Development and SDK Features|| SDK Generator Installer UI|| Look at different ways of Installer UI (GTK+ and ncurses) seems none of them is the right choice, decide to go with script to implement all the functionalities of installer and later add UI part on top of it || 1||Done|| Jessica|| jzhang|| Enhancement
|-
|| Tool Development and SDK Features|| Customize sysroot setup || Add and test out "--sysroot" config option to cross compiler within Eclipse IDE || 1|| Done || Jessica|| jzhang|| Enhancement
|-
|| Tool Development and SDK Features|| SDK Generator Installer design revision|| Close all open questions regarding Yocto SDK Generator Installer function design and come up HLD || 1|| Done || Jessica|| jzhang|| Enhancement
|-
|| Distribution / components|| kernel version|| keeping 2.6.34 as a -stable kernel is the best option. I've also got a newer -devel tree that can be made available or made the default. || 3|| 2.6.37 is now running regression, heavy lifting done, Done by Dec 03 || Bruce|| bruceashfield|| enhancement
|-
|| || assign Yocto Project PM|| acquire and assign a program manager for Yocto Project|| || WIP, Interview candidates by Dec 3, Dave commits to end of year || DaveST|| || 
|-
|| || assign Yocto Project Sys Admin|| || || WIP, two candidates good, likely to start Dec 13 || Saul|| || 
|-
|| Distribution / components|| Zypper/RPM|| Small write-up of the problems we're having w/ Zypper and what we plan to do. (i.e. create a roadmap/design)   - Includes rootfs generation   - Package uprev/install/removal || 1 || WIP, Done by Dec 06 || Mark || || 
|-
|| Tool Development and SDK Features|| oprofileUI|| Fixing various bugs of the oprofileUI to make it workable on big endian host.(i.e. ppc, mips) || 2 || WIP, bugs fixed, Josh work with Richard and oprofileUI maintainer (robsta) for upstreaming. WIP, done by Dec 10 || Jessica || lianhao.lu || Bug #382 / Bug #493
|-
|| Poky Feature|| SDK Version Control|| If we can expect that yocto SDK has lots of release in the future, we might need to consider SDK version control. Currently, every thing installed under /opt/poky which leads to things be overriden, we need to be able to use a scheme like /opt/poky-1.0, /opt/poky-2.0 to distiguish things. || 2|| Patch done, waiting for RP's return from holiday.  WIP, done by Dec 08 || rpurdie|| jzhang|| Enhancement
|-
|| Kernel || Kernel plan complete || Flesh our kernel deliverables and add to Yocto 1.0 schedule || || Done|| Darren || dvhart ||
|}

=== Sprint C (closes Nov 26, 11:59pm PDT -- pull request sent, initially reviewed) :: NOTE: this is US Thanksgiving week ===

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Distribution / components|| Distro Audit: Licence Checksums|| Make the licence checksums fatal if not present || 1|| WIP, done by Dec 10 || Saul|| rpurdie|| Hygiene
|-
|| Poky Features || Performance Analysis Completed|| "I'd like someone to instrument a green release build, see where it spends time (hot/cold parsing time, individual task building time) and then compare this with our 0.9 release build. I'd also like to compare the disk usage between the two. Once we have a blame list we can then set about fixing it. Some things I know will come up: a) pseudo, b) checksums/signature code, c) exec() vs fork for executing tasks, d) task based prebuilds increasing disk usage, e) rpm dependency calculations, f) using rpm vs. ipk but I may be wrong and there may be others. We need numbers. "|| 1|| WIP, done by Dec 08 || Saul / Qing, Dongxiao|| rpurdie|| Enhancement
|-
|| Poky Features || environment variables for kernel builds|| switching a branch, or adding a configuration feature (and even changing the kernel repo) is often done during development of a BSP. Having some additional variables that are pass the bitbake environment scrub would be useful. i.e. KBRANCH=foo bitbake -c configure linux-yocto. This goes along with the other BSP bootstrapping suggestions. || 2|| WIP, done by Dec 06 || Bruce|| bruceashfield|| Enhancement
|-
|| Poky Features || kernel development layer|| The (correct) poky behaviour of building known revisions coupled with the fetcher requiring a BSP branch to already be present means that local modifications (and kernel source tree) are required for kernel development. I already have a layer that overrides/modifies the behaviour when added to the bblayers.conf and configured into an environment. This seems useful for more people to use. || 2|| WIP, done Dec 06 || Bruce|| bruceashfield|| Enhancement
|-
|| Distribution / components|| Zypper/RPM|| RPM Uprev / Zypper Uprev  [lets get to the latest versions]|| 1|| Starting, done by Dec 10, very doable|| Mark|| || 
|-
|| Supported Targets|| ARM Platform Support|| Replace beagleboard with pandaboard (??)|| 2|| Pandaboard on order, patches being collected, blocked on h/w delivery || Bruce|| alex|| Basic Yocto hardware support 
|-
|| Distribution / components|| push of all relevant Wind River patchs to Yocto (patch comparison)|| Ensure patches present to packages in WRS are also in Poky|| 1|| WIP, on track for completion by Dec 03|| Mark|| Mark|| 
|-
|| Distribution / components|| Security Process|| We need a dedicated person to scan and apply critical security updates to the distro. The MeeGo team already has a similar process with some scripts which may be leveraged. To complete the task, the process should be documented and a first pass over the metadata made to establish the current position on security. Any upgrades needed should be identified and a plan to address them should be in place but doesn't have to be implemented by this point.|| 1|| WIP, done by Dec 08 || ScottG|| ktian1|| enhancement
|-
|| Tool Development and SDK Features|| SDK Generator Installer Opkg repo design|| Come up a opkg repo design that will mimic the final Yocto package repo layout to be used by SDK Generator Installer to test against|| 2 || Done || Jessica || jzhang || 
|-
|| Tool Development and SDK Features|| Yocto Installer tar creaion|| Create a Yocto Installer tar ball which contains Installer script and supported opkg component that will be used for installing other Yocto components|| 2 || Done || Jessica || jzhang || 
|-
|| Documentation|| Kernel Framework Paper from WR|| The paper from WR needs to be re-written and then posted somewhere on the Yocto Project site.  This will involve examiniation of the text and re-writing and formatting for presentation.  Currently it is simply a text document.  Completion time assuming uninterrupted time is one week.|| High|| WIP will be online with Concepts clean up by Dec 03 || Scott Rifenbark|| 1 Week|| Documentation
|-
|| Documentation|| Poky Reference Manual|| This guide exists in the 0.9 form.  The re-write of the text needs to be completed.  So far, all the chapters have been rewritten but not re-posted on the site.  Only the appendices remain for a text scrub.  Time to complete this would be a week of uninterrupted time.  Ideally, the manual would be a sub-manual that would be referenced and architected into the Yocto Project Development Guide.|| Medium|| Done|| Scott Rifenbark|| 1 Week|| Documentation
|-
|| Kernel || Initial meta-linaro layer || meta-linaro layer providing a kernel, tool-chain, and uboot loader. This deliverable is primarily to get the infrastructure in place and have a buildable kernel. Toolchain on best effort basis. || || WIP, Kernel builds. Various build environment issues remain. Layer will contain kernel, gcc, gdb and uboot. Would like this task done by Dec 3 (kernel done, toolchain Dec 03). || Darren || dvhart || Moderate risk of slippage due to holidays.
|-
|| Kernel || Tracing: blktrace and sysprof recipes || || || Blktrace patch submitted, sysprof by Dec 03 || Tom || dvhart ||
|}

=== Sprint D (closes Dec 3, 11:59pm PDT -- pull request sent, initially reviewed) :: NOTE: week of the F2F planning meeting ===

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Distribution / components|| Zypper/RPM|| Integration based on design from Sprint B|| 1|| Will push to Sprint E|| Mark|| sgw|| Functionality
|-
|| Tool Development and SDK Features|| Yocto Installer for SDK Generator Installation functions support||This really 2 features: 1. SDK Generator installer - Currently you have to download an SDK toolchain, a qemu kernel and a qemu rootfs, then merge these things all together. Instead we should separate these out into the following blocks:     * SDK core (inc. installer),     * 32 bit native tools,     * 32 bit compiler [for each arch],     * 64 bit native tools,     * 64 bit compiler [for each arch],     * Target kernel+rootfs [for each arch],     * Optional extra lib 'packs' [for each arch]. 2. Customize sysroot setup -  The target roofs would be used both by qemu *and* as the SDK sysroot at a user appointed location. The installer would be a script that will setup host toolchain and native tools under /opt/poky, and target sysroot under user specified location|| 1|| WIP, done Dec 06 || Jessica|| rpurdie|| Enhancement
|-
|| Tool Development and SDK Features|| Yocto Installer support for image-creator and needed yocto-metadata design||Come up design what need to be created as packages to support using "opkg install" for  image-creator and needed yocto-metadata|| 2|| Targeted for Dec 08 || Jessica|| rpurdie|| Enhancement
|-
|| Distribution / components|| perl upgrade|| perl is the most cross un-friendly recipe pending upgrade. || 2|| Slipping due to Linaro layer, moves to end of Sprint E || Nitin|| Nitin Kamble|| enhancement
|-
|| Kernel || Kernel git branching structure revamped || || 1 || WIP, done by Dec 06 || Bruce || dvhart ||
|-
|| Kernel || Tunnel Creek (Crown Bay) || || 1 || Have HW, on track for Dec 03 || Tom || dvhart ||
|}

=== Sprint E (closes Dec 9 (THURSDAY), 11:59pm PDT -- pull request sent, initially reviewed)  ===

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Distribution / components|| Distro Audit: Upgrades Completed (Phase 1)|| Update to new versions as per the agreed plan for M2 from Sprint A|| 1|| Review|| Saul|| rpurdie|| Continual Maintenance
|-
|| Poky Features || Fetcher Overhaul|| "The highlight summary would be merging of the fetch and unpack tasks. This would mean we could put git checkouts directly into WORKDIR/git and do fetching/handling of SCM based checkouts much more efficiently as we'd no longer have to tar/untar but could do a referenced clone. WORKDIR could be made a directory without the revision in the name so when the version increments, the WORKDIR can just be updated by the SCM and rebuilt. I'd propose we rewrite the fetcher code as lib/bb/fetch2, then switch poky over to use it, leaving the fetch directory around until we can get to it. Related to this task is storing SRCREV knowledge from the recipes at parse time for access by the bitbake core, there is an open bug about this enhancement. We can then nuke the central revisions file in the distro directory which users hate. Also, the fetcher should be checking the validity of what it does - checksums for everything in SRC_URI except file:// and scm urls. "|| 1|| Risk of slipping to M3SA || Saul / Ke, RP|| rpurdie|| Enhancement
|-
|| Distribution / components|| Distro Audit: Src Checksums|| Make sure all SRC_URI components have checksums too (fatal if not) || 1|| WIP || Saul|| rpurdie|| Hygiene
|-
|| Poky Features || enable KVM with qemu|| today all new Intel processors support VT, which are enabled on most desktop machines which are most frequently used build machine. with VT support, x86/x86-64 qemu target runs faster which is a good thing for emulation environment. This may require some qemu option tweaks and also poky-qemu script enhancement. || 2|| on track|| Saul / Edwin|| ktian1|| Enhancement
|-
|| Poky Features || libtool sysroot option|| libtool 2.4 has a sysroot option. We should try and use it, see how it works and whether we can ditch some of our libtool hacks. || 1|| on track || Saul / ScottG || rpurdie|| Enhancement
|-
|| Poky Features || Performance Enhancement Completed|| "I'd like someone to instrument a green release build, see where it spends time (hot/cold parsing time, individual task building time) and then compare this with our 0.9 release build. I'd also like to compare the disk usage between the two. Once we have a blame list we can then set about fixing it. Some things I know will come up: a) pseudo,b) checksums/signature code, c) exec() vs fork for executing tasks, d) task based prebuilds increasing disk usage, e) rpm dependency calculations, f) using rpm vs. ipk but I may be wrong and there may be others. We need numbers. "|| 1|| on track but some dependent on pseudo updates || Saul / Qing, Dongxiao || rpurdie|| Enhancement
|-
|| Distribution / components|| User specified qemu config support|| We'll provide user an edit box which allows advanced qemu user to specify arbitrary qemu configuration to meet their needs, which the poky-qemu scrip will just append the config list towards the end of the list of parameters to bring up qemu,  it also expect the poky-qemu script to do some basic sanity check on the user specifications to catch the obvious mistake || 2|| on track || Saul / criping || criping|| enhancement
|-
|| Documentation Features|| Package report system|| finish major feature development and internal review [setup a package report system in an internal machine. We need push it publicly available. The basic features like search and report have been there. But there're still some enhancements in plan, to make it a fit place to feel Yocto metadata comfortably]|| 2|| mostly in place, on track || KevinT / Lei || ktian1|| enhancement
|-
|| Tool Development and SDK Features|| SDK Version Control support in SDK generator installer|| If we can expect that yocto SDK has lots of release in the future, we might need to consider SDK version control. Currently, if we un-tar the sdk, it will override the older version. It's not good for app developers since they might need the old version to do something. And also, maybe a finer installer than untar is preferred. Installer will tied to certain SDK version and the installation will go under /opt/poky-versionNo.|| 1|| on track || Jessica|| criping|| Enhancement-expect planning process by Jessica to handle this task.
|-
|| Kernel || New kernel recipes || dev, -devel, -custom || 3 || on track for Dec 06 || Bruce || dvhart ||
|-
|| Kernel || Initial meta-rt layer || PREEMPT_RT kernel and related test-cases and benchmarks || 2 || blocked on community feedback, move to M3SA || Darren || dvhart ||
|-
|| Kernel || Tracing: Initial SystemTap recipe || || 3 || on track || Tom || dvhart ||
|-
|| Swabber || Documentation for swabber || || 1 || on track || Alex ||  ||
|-
|| CCB || Defect triage process in public documented and implemented || || 1 || || Saul ||  ||
|}

== M3 (Dec 20 to Feb 08 -- Dev Complete Feb 04, Stabilize Complete Feb 11, Release Complete Feb 18) ==
=== Sprint A (closes Dec 24, 11:59pm PDT -- pull request sent, initially reviewed) ===

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Distribution / components|| Distro Audit Upgrades Planned (Phase 2)|| Complete plan for package upgrades in M2|| 1|| Review|| Saul|| || Continual Maintenance
|-
|| Distribution / components|| MACHINE or Recipe specific sysroots|| Each machine should have its own sysroot. We'll probably have to split do_populate_sysroot into a two step process, creation of the package and than installtion of the package, which the installation of the package being made machine specific (put ${MACHINE} into ${STAMP} and bitbake should do that). Also allowing this to work per recipe would be desireable|| 1|| Review|| Saul || rpurdie|| Hygiene
|-
|| Distribution / components|| Toolchain Bootstrap Process|| The toolchain as it bootstraps overwrites files like libc.so and libgcc.so in the sysroot directory which causes issues if you just try and rebuild part of the toolchain. Each step of the bootstrap process should use a separate sysroot. Once this is once, sstate file overwriting detection can be added and enabled. || 1|| Review|| Saul|| rpurdie|| Hygiene
|-
|| || Multilib Support|| || 1|| || Richard|| || 
|-
|| Validation|| Alpha testing complete|| 4-5 internal developers unfamiliar with Yocto Project try to do a build and report on the experience and issues encountered|| 1|| Accept|| PM|| davest|| 
|-
|| Tool Development and SDK Features|| Eclipse poky tree interfacing (git support)|| Use Eclipse git capability to install poky tree from git repo and able to interact with git repo at file level within Poky tree || 2|| Review|| Jessica|| jzhang|| Enhancement
|-
|| Tool Development and SDK Features|| Eclipse poky tree interfacing (metadata file editor)|| Provide a metadata file editor with some syntax checking and keywords highlight capabilities|| 2|| Review|| Jessica|| jzhang|| Enhancement
|-
|| Tool Development and SDK Features|| IDE Project templates|| Templates for various project types: Clutter GUI, Gtk+ GUI, to help developers get started quickly || 2|| Review|| Jessica|| josh|| Enhancement
|-
|| Tool Development and SDK Features|| push TCF/RSE patches upstream|| work with community to finish up our TCF terminal service, TCF/RSE integration remaining patches taken by upstream. Blocking issues including Eclipse Bug #327865 || 1|| WIP, minor issues, slip out to Sprint C or D|| Jessica|| jzhang|| Enhancement
|-
|| Documentation|| SDK Reference Guide|| This would be a guide for developers using the SDK.  Ideally, the manual would be a sub-manual that would be referenced and architected into the Yocto Project Development Guide.  The manual has not been scoped and would take a week to scope.  I have no idea of the length.  Industry writing standards dictate that three to four pages of a manual can be developed per day.  So, a 30 to 40 page manual would take a couple of weeks.  However, these are just standards that are use for general estimates and assume dedicated, non-interrupted time.|| High|| Not Started|| Scott Rifenbark|| 3-4 Weeks|| Documentation
|-
|| Kernel || Tracing: trace-cmd python binding cleanup || || 3 || || Darren || dvhart ||
|-
|| Kernel || Tracing: KernelShark, tuna, oscillosope recipes || || 3 || || Tom || dvhart ||
|-
|| Pseudo || Pseudo enhancement to enable on/off switch || || 1 || || Mark ||  ||
|-
|| Pseudo || Bitbake enhancement for pseudo on/off switch || || 1 || || Richard ||  ||
|-
|| Swabber || Complete review of swabber outputs || || 1 || || Alex ||  ||
|-
|| bugzilla || Complete restructure of bugzilla categories || || 1 || || Saul ||  ||
|}

=== Sprint B (closes Jan 07, 11:59pm PDT -- pull request sent, initially reviewed) ===

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Distribution / components|| Distro Audit Documentation Output|| Audit package documentation output || 2|| Review|| Saul / ScottG || rpurdie|| Hygiene
|-
|| Poky Features || Bitbake multi-threaded parsing|| Bitbake recipe parsing is currently single threaded. I want to make this multithreaded as the speedup would be nice. If I can only take a single task for myself for 1.0, I'm nominating this one as I enjoy this kind of thing and I have ideas on how to do it. || 1|| Review|| Richard|| rpurdie|| Enhancement
|-
|| Distribution / components|| Lock in Kernel/Toolchain version|| || || || Richard|| || 
|-
|| Distribution / components|| License Update|| For each of the licences we support, I'd really like to have a licences directory with a copy of that license contained within. When it comes to deciding what a given LICENSE field means, this would be the reference. It also means we can include the licences a given image includes with the image. This continues to make our license handling world class and ahead of the field. || 2|| Review|| Beth|| rpurdie|| Hygiene
|-
|| Poky Features || DSO linking changes|| "By the default the gcc linker will automatically link any dependant objects/libraries. ""Inherited"" linkages can cause issues, for example, where a shared object changes its dependencies but a program has come to rely on symbols from an implicitly linked library. Fedora implemented this change in F13, seems like it would be useful to have in Poky too. "|| 2|| Review|| Saul|| josh|| bug#516
|-
|| Distribution / components|| rootless X|| rootless x server has better security than x server launched by root. MeeGo already enable this feature. it would be nice for Yocto to also enable it. || 2|| Review|| Saul|| yuke|| enhancement
|-
|| Tool Development and SDK Features|| Qemu configuration change|| Provice edit box for advanced user to specify qemu configurations|| 2|| Accept|| Jessica|| criping|| 
|-
|| Tool Development and SDK Features|| Eclipse Poky tree interfacing (bitbake commands support)|| Support user run bitbake commands within CDT console|| 2|| Accept|| Jessica|| jzhang|| 
|-
|| Tool Development and SDK Features|| Lock down Eclipse+CDT+TCF version|| || 1|| Accept|| Jessica|| || 
|-
|| Documentation|| Migration chapter in the Poky Reference Manual|| This chapter would cover the four identified use-cases for migrating up to the most recent version of Yocto Project.  Additionally, it would cover migration scenarios from other development systems.  The chapter does not yet exist.  The chapter has not been scoped outside of having a meeting that identified four use-cases that did not include migration from a development system outside of Yocto Project.  It will take some more scoping time to cover those areas (a day or two).  Again, I have no idea of the length.  See earlier entries for standard industry writing estimates for software documentation|| Medium|| Not Started|| Scott Rifenbark|| 3-4 Weeks|| Documentation
|-
|| Supported Targets|| Intel Platform Support|| JasperForest|| 2|| Accept|| Tom|| davest|| Basic ECG support (Moved from Sprint A)
|-
|| Demo|| Finalize on demo plans for v1.0 launch || || 1|| Accept|| Dave || || 
|-
|| Release || Release plans for v1.0 launch || Fill out the M4 plan with the necessary release activities and timings || 1|| || Beth || || 
|}

=== Sprint C (closes Jan 14, 11:59pm PDT -- pull request sent, initially reviewed) ===

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Poky Features || Poky Image Creator|| A standalone application you can run which asks you to select a distro and machine, then presents a list of packages you can select. Once the selection is made, it goes off and bakes you an image which is then presented to you. Implementation wise, it should use the sstate packages, be a bitbake UI and use the usual poky bbclass files to do the image construction behind the scenes. || 1|| Review|| Josh|| rpurdie|| Enhancement
|-
|| Validation|| Boottime/Performance Analysis|| Compare Yocto Project performance to other projects such as MeeGo|| 1|| Review|| Tom|| davest|| project commitment 
|-
|| Distribution / components|| LSB Sanity|| execute LSB Test and improve passing rate and document failures with clear understanding|| 2|| Review|| MarkH/Saul|| sgw|| Hygiene
|-
|| Distribution / components|| Review & Fix Standards Tests|| Review the results from LTP, POSIX and asses the result, fix as appropriate and clearly document failures.|| 2|| Review|| Saul|| sgw|| Hygiene
|-
|| Tool Development and SDK Features|| (Bitbake commander)Poky tree interfacing integration|| Integrate all the features to support poky tree interfacing withing Eclipse IDE: poky tree install from git repo, edit metadata file using editor, commit back changes to git repo, and run bitbake commands withing CDT console|| 2|| Review|| Jessica|| jzhang|| Enhancement
|-
|| Kernel || Tracing: perf trace marger support || This is from feedback to the new trace command. Ingo appears to have this nearly complete already. || 3 || || Darren || dvhart ||
|-
|| Kernel || Tracing: perf trace scripting support || || 3 || || Tom || dvhart ||
|-
|| Cleanup || bitbake user experience error handling validation completed || || 2 || || Richard ||  ||
|-
|| Cleanup || variable scrub - ensure all metadata variables are documented || || 2 || || Scott/Darren ||  ||
|}

=== Sprint D (closes Jan 21, 11:59pm PDT -- pull request sent, initially reviewed) ===

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Documentation Features|| Package report system|| move to public server [setup a package report system in an internal machine. We need push it publicly available. The basic features like search and report have been there. But there're still some enhancements in plan, to make it a fit place to feel Yocto metadata comfortably]|| 2|| Review|| KevinT|| ktian1|| enhancement
|-
|| Tool Development and SDK Features|| Yocto Installer image-creator and needed poky-metadata support|| The poky build system will build packages for image-creator and needed poky-metadata, which the Yocto Installer will be able to use "opkg install" to install them|| 2|| Review|| Jessica|| rpurdie|| Enhancement
|-
|| Distribution / components||Add headers and libraries to qemu images ||Since we'll be using qemu images as target sysroot, need to create a set of qemu images for minimal, sato, LSB that contains target header and libraries.|| 2|| Review|| Saul||jzhang|| Enhancement
|-
|| Distribution / components|| push of all relevant Wind River patchs to Yocto (patch comparison)|| Update any additional patches needed since M2.|| 1|| Review|| Mark|| Mark|| 
|-
|| Distribution / components|| mklibs|| mklibs is a tool to optimize size of [e]glibc for a perticular root file system image. It is useful to save disk space on small devices. || 2|| Review|| Saul|| Nitin Kamble|| enhancement
|}

=== Sprint E (closes Jan 28, 11:59pm PDT -- pull request sent, initially reviewed) ===

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Supported Targets|| Intel Platform Support|| Sandybridge|| 2|| Accept|| Tom|| davest|| Basic ECG support
|-
|| Tool Development and SDK Features|| SDK user workshop|| Have some developers sit down and use our tools to develop demo software for Yocto. || 2|| Review|| Jessica|| josh|| Enhancement
|-
|| Documentation|| Yocto Project Development Guide|| This manual would be an over-arching document that frames the complete development cycle within Yocto Project.  The idea here is that the document would be an umbrella document that spawned and referenced subsequent documents.  The organization would be the first chapter overviewing the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc.  Scoping would be about two weeks and length would probably be about 40 pages.  Overall development time would likely be a month of uniterruped time.|| Medium|| Not Started|| Scott Rifenbark|| 3 Weeks|| Documentation
|-
|| Kernel || Final linux-yocto_git.bb || With 2.6.37 kernel || 1 || || Bruce || dvhart ||
|-
|| Kernel || Final meta-linaro layer || || || || Darren || dvhart ||
|-
|| Kernel || Final meta-rt layer || || || || Darren || dvhart ||
|-
|| Kernel || Sandy Bridge || || 1 || || Tom || dvhart ||
|}

=== Sprint F (closes Feb 03 (THURSDAY), 11:59pm PDT -- pull request sent, initially reviewed) :: NOTE: China New Year Holiday ===

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| || || || || || || || 
|}

== M4 (Feb 07 to Apr 15 -- Stabilize Complete Mar 18, Release Complete Apr 01, Contingency to Apr 15) ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| || || || || || || || 
|}

== Features needed and to be put into sprints by assigned owners: ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Poky Features || package config option enhancement|| there're several enhancements we may do here:     * allow users setting specific config options (local or global) from external tool, such as poky image creator, instead of changing recipes manually. Need a mechanism to convert from variable assignments into exact config options (e.g. feature_${PN} = ""1"" -> ""--enable-feature""). Consequently dependency chain needs update with option status.     * host contamination check. We have swabber to check host contamination, but I'm not sure whether it covers configuration phase. If not, this is one area to improve, as not ususually we see configure script checks host bits for available features    * conditional option manipulation. In many recipes we enable/disable one option based on availability of other packages. Now this is done manually and not flexible. this should be made automatically though some new annotation to indicate condition, or just base_contains (not convenient: long line, need define distro features) || 2|| Review|| Richard/MarkH|| ktian1|| Enhancement
|-
|| Distribution / components|| performance indicators|| define some indicators (boot time, footprint, build time, power, component benchmarks, etc.) and then collect them for tracking purpose. The result could be posted on the wiki site, and the initial indicators can be easy ones which can be easily retrieved from autobuilder or weekly qa report). This way we have a clear track about the healthy of the Yocto project, and also identify weak areas. We can include qemu targets and several representational boards as the targets. || 2|| Review|| Beth/Jiajun|| ktian1|| enhancement
|-
|| Media|| Yocto Project Awareness Video|| This 2.5 minute video would introduce and describe the benefits of Yocto Project.  The video would use entertaining animations that described concepts and benefits.  The result would be suitable for YouTube, conferences, and the website.  The production is called an "Epipheo" and will be created by Epipheo Studios.  The engagement process has begun and the kick-off meeting will be soon.  The PO is in place.  Time for development is 10 weeks.|| High|| Kick-off Imminent|| Scott Rifenbark|| 10 Weeks|| Media
|-
|| Documentation|| Yocto Project Debugging Guide|| This would be a guide for the debugging and bug tracking process in Yocto Project.  Originally, the thought was that we needed a Bugzilla User's Manual.  However, since we don't own Bugzilla it doesn't make sense to produce documentation for it.  Rather, we should document the process as it fits into the Yocto Project environment.  Ideally, the manual would be a sub-manual that would be referenced and architected into the Yocto Project Development Guide.  The manual has not been scoped and would take a week to scope.  Again, I have no idea of the length.  See the previous item for standard industry writing estimates for software documenation.|| Medium|| Not Started|| Scott Rifenbark|| 3-4 Weeks|| Documentation
|-
|| Website|| Yocto Project Website|| The 0.9 website is in place but needs updates.  Items for consideration are the left-panel naviagation scheme, a contributions guidance page, color-scheming and theme (possibly).|| Medium|| Not Started|| Scott Rifenbark|| 1-2 Weeks|| Website
|}

== Features not believed to be needed in v1.0: ==

{|border="1"
|| '''Group''' || '''Feature Name''' || '''Description''' || '''Priority''' || '''Status''' || '''Owner''' || '''Source''' || '''Comments / Bugzilla Links'''
|-
|| Poky Features || OpenEmbedded/Bitbake Upstreaming|| "We firstly need to review where we are and where OE is. We then need to make a plan about what we're going to push upstream and what we're not. I'd suggest when we're in PRC, we do a crash course in ""dealing with OE"" and then many dedicate a block of time (a week) where the distro team comes up with a patch set we then propose and get merged into OE. I'd like to find a couple of interested people to monitor OE more regularly and start a workflow of things between Poky/OE where appropriate. The key thing to remember is we need to keep the architectures compatible. The team is now at the point where I'm happy for them to actually try building OpenEmbedded and not worry about it tainting them! "|| 2|| Review|| || rpurdie|| Process
|-
|| Poky Features || Handle old versions in WORKDIR|| an incremental build directory may finally include many old versions WORKDIRS. It'll be good to have those old versions tracked in the cache, which can then either generate a report or allow selectively cleaning up an specific version WORKDIR. Or else it's difficult to figure it out when people want to keep the whole tmp directory but like to cleanup some old bits when disk usage is under pressure. If it's not easy to do in bitbake, perhaps some separate scripts would be also helpful || 3|| Review|| || ktian1|| Enhancement
|-
|| Poky Features || run bitbake w/o rebuilding the cache|| "sometimes it's useful to allow run bitbake w/o re-parsing recipes, if we know nothing metadata is changed. we can just allow reusing existing persistent cache. this is useful when people is debugging WORKDIR w/o metadata change. also sometimes ""bitbake -e"" is used frequently to check poky variable information. with existing cache, several seconds can be saved which are not negligible for a developer daily working on Yocto "|| 2|| Review|| || ktian1|| Enhancement
|-
|| Poky Features || parallel make improvement|| parallel make experience is not good, especially when bb threads and make threads are increased larger than 8. So far we either try to fix package makefile or mark the recipe as no parallel make, when build faiures are reported. But this greatly impacts user experience for a successfully continuous build process. Could we define a safe number we do want to support for 1.0 release? and then have our autobuilder, QA test, and developers cover that number immediately and fix any issues accordingly. Then the safe number can be suggested to the Yocto user || 2|| Review|| || ktian1|| Enhancement
|-
|| Poky Features || Dependency packages rebuild/clean|| It is a mechanism to rebulid or clean a package and all other packages which have build/runtime dependency on it. With this change, we can find potential influences of package upgrade to its related packages, which can make the incremental build more trustable. For example, if we upgrade a package to a new vesion which changes its API, this mechanism can easily find out the incompatibility to other packages which have dependency on it. || 2|| Review|| || dongxiao.xu|| Enhancement, replaced by checksum feature
|-
|| Distribution / components|| FOSSology|| This may be similar to License Update above, but start to use FOSSology to track licenses. || 2|| Review|| || sgw|| Hygiene
|-
|| Distribution / components|| Package Developer Tools|| Create a set of Init scripts template and then review our current init scripts and modify them to confirm to the template. || 2|| Review|| || sgw|| Easy of Use
|-
|| Distribution / components|| Package Website|| Complete the work the intern has started on generating the distro tracking information and get it out on the external site. || 2|| Review|| || sgw|| "Hygiene, duplicate of ""Package report system"""
|-
|| Distribution / components|| Bluetooth UI support|| Currently we have bluez package in poky, and we need to have a workable graphic user interface to connect/configure BT devices. One choice may be gnome-bluetooth-applet. || 3|| Review|| || dongxiao.xu|| enhancement
|-
|| Distribution / components|| Connman-gnome enhancement features|| Enable connman-gnome to support features like, WPA Enterprise connection, hidden SSID, etc. || 3|| Review|| || dongxiao.xu|| enhancement
|-
|| Distribution / components|| Java Running Environment support|| Since most embedded systems support java applications running in it, maybe we'd better consider supporting some kinds of JVMs(Embeded JVM). The JVM may not run by default, but user can launch it if running java applications. Compared with GTK/QT, java user number is not small too. || 3|| Review|| || criping|| enhancement
|-
|| Distribution / components|| create more use cases|| UPnP demo is one really good use case showing how Yocto is utilized to make real functionality. and we could create more to show how Yocto is easily adapted to real use cases. Those use cases can be either maintained as seperate demo layers in yocto repo, or in seperate branches for reference. We can also call for community's contribution on this which would make 1.0 full-fledged. Or else the newbies to Yocto may be in puzzle how our sample profiles can satisfy their requirements. || 2|| Review|| || ktian1|| enhancement
|-
|| Distribution / components|| i18n support || internationalization is an important system wide feature. Many component like font, locale affect the i18n. Yocto alreay has some i18n related package like pango, but so far did not consider i18n systematically. so this is place holder to systematically add i18n support. || 2|| Review|| || yuke/qing|| enhancement
|-
|| Distribution / components|| more demos || demos are a good way to educate, push the envelope, and at the same time tout the strengths of the platform. This item just records a current set of ideas from various sources which could/should be implemented:    * face-recognition/face-finding,     * robotic control/application of face-finding to 'camera-as-sensor' (hexbug demo),     * others [tbd, add here]|| 2|| Review|| || tzanussi|| enhancement 
|-
|| Tool Development and SDK Features|| Provide qemu management UI|| In current eclipse plugin, QEMU settings are put together with project configuration. So we can only have limited settings. If we can have a separate QEMU management UI, the end user could firstly create a QEMU config, such as (env file of arch, image location, unfs or not, sato or lsb, mem size, disk size). And then he can launch a QEMU with a specific config. The dependency between project configuration and QEMU config will be resolved. After all QEMU has nothing to do project configuration. Need to careful review the UI to ensure minimal impact to testing matrix. || 3|| Review|| || criping|| "Enhancement, duplicate of ""Qemu mem/disk size can be adjusted"""
|-
|| Tool Development and SDK Features|| QT plugin For Eclipse|| Integrate QT Ecplise plugin and extend for Yocto Project || 3|| Review|| || jzhang|| Enhancement
|-
|| Tool Development and SDK Features|| Profiling/Trace GUI's|| We have a wealth of great tracing and profiling tools but the UI's for them are all extremely minimal and usually quite ugly. Would be great if we could compete with, or even better, Apple's offerings here. We have the technology! || 2|| Review|| || josh|| "Enhancement, duplicate of ""Tracing/Profiling Planning Complete"""
|-
|| Tool Development and SDK Features|| Other profiling tools|| Complete Tom's review of profiling tools and architecture || 2|| Review|| || josh|| "Enhancement, duplicate of ""Tracing/Profiling Planning Complete"""
|-
|| Tool Development and SDK Features|| Design next-gen tracing/profiling tools|| Yocto 1.0 will include all the essential existing tracing/profiling tools expected by users, and Josh has proposed a UI integration of all those tools as far as it's possible to do so. That level of integration, basically a 'plugin-level' integration is necessary and useful, but doesn't go far enough. A next-generation tracing tool would integrate at a much more fundamental level; if done properly, it would provide unmatched levels of power and usability to users, and would allow Yocto to distinguish itself in the embedded tracing/profiling space in a way also unmatched by any other distro/build-tool. The implementation would of course not be available for Yocto 1.0, but a coherent design, including prototypes, that could be taken to the community and implemented in a V 1.5 or 2.0 should be done in that time frame. || 1|| Review|| || tzanussi|| "Enhancement, duplicate of ""Tracing/Profiling Planning Complete"""
|-
|| Documentation Features|| Self Documentation of image contents|| "I'd like to see the -doc packages Poky builds being combined into some kind of large documentation index representing the collective API docs of the target being built. This can then be placed on a webserver and viewed over the web. We'd have a demonstration of this for a ""bitbake world"" target. Part of the idea here is to start making good use of the docs as if developers see this they might start writing better docs too. Aim is to lead the field :). There are a number of places poky packages disable doc generation due to missing tools so we'd need to add these so we can enable the doc generation. Many packages already have many docs though too. "|| 2|| Review|| || rpurdie|| enhancement
|-
|| Validation|| Testing Framework|| Add a framework for doing automated testing in the project|| 1|| Review|| || davest|| project commitment
|-
|| Validation|| more SDK builds on autobuilder|| enable more SDK related tests on autobuilder such as meta-ide-support, etc.|| 2|| Review|| || ktian1|| project commitment, addressed by test plan (?)
|-
|| Validation|| more people should try using SDK|| this may not be a feature, but a requirement. SDK including meta-toolchain is one key factor impacting user experience on Yocto. It's not enough to have only SDK team play with it|| 2|| Review|| || ktian1|| project commitment, addressed by test plan (?)
|-
|| Validation|| Unit Testing Framework|| Add a mechanism to bitbake to parse source packages that have unit tests and then execute them on the target|| 3|| Review|| || sgw|| "project commitment, duplicate of ""Testing Framework"""
|-
|| Validation|| Test Case open source|| Open source Yocto test cases with xml format|| 1|| Review|| || yyou|| "project commitment, duplicate of ""Testing Framework"""
|}