Yocto Project - User contributions [en]

Yocto Project v1.1 Release Criteria

2011-06-07T14:47:37Z

Jnfleisc: /* Yocto Project 1.1 */

The Release Criteria for the various Yocto Project 1.1 releases are below.

= Yocto Project 1.1 =
{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''
|-
| Functional Completion || All M1 features and BSPs are in the build. || bgcolor="#39FF14" | [[File:Schedule-status.PNG]] All desired features are in build. One documentation publishing fix remains. see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for details
|-
| Build and Release (Yocto) || All M1 features can be built with no errors. || bgcolor="#39FF14" | Build pulled in all fixes possible.
|- Working
| Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="#39FF14" | Build pulled in all fixes possible.
|-
| Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor="#39FF14" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW NEW bugs] - 2 unaccepted New bugs for 1.1 M1 [http://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&columnlist=bug_severity%2Cpriority%2Ctarget_milestone%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc&priority=High&query_format=advanced&target_milestone=---&target_milestone=0.9%20M1&target_milestone=0.9%20M2&target_milestone=0.9%20M3&target_milestone=0.9%20M4&target_milestone=0.9.1&target_milestone=0.9.2&target_milestone=1.0%20M1&target_milestone=1.0%20M2&target_milestone=1.0%20M3&target_milestone=1.0%20M4&target_milestone=1.1&target_milestone=1.1%20M1&target_milestone=1.1%20M2&target_milestone=1.1%20M3&target_milestone=1.1%20M4&target_milestone=Q1&target_milestone=Q2&target_milestone=Q3&target_milestone=Q4&query_based_on= HIGH priority bugs] - no HIGH priority bugs for 1.1 M1 See trend chart at https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="#39FF14" | https://wiki.pokylinux.org/wiki/Yocto_1.1_Milestone_Test_Report
|-
| Distros Tested || Fedora, Ubuntu, Opensuse || bgcolor="#39FF14" | Fedora 14, Ubuntu 11.04, Opensuse 11.4
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="#39FF14" | https://wiki.pokylinux.org/wiki/Yocto_1.1_Milestone_Test_Report
|-
| Documentation || M1 documentation deliverables are complete. || bgcolor="#39FF14" | Only deliverable is allowing documentation to be updated even after code freeze. On-track.
|-
| Build Performance || Plan for improving performance is defined. || bgcolor="#39FF14" | Performance goals for M1 (mostly planning goals) were met. See schedule for details. Build is at 102 minutes.
|-
| Upstream Commits || Have upstream status updated on 90% of patches (so that we can have a status update) || bgcolor="#39FF14" | At 85%, which is good enough for alpha.
|-
| Marketing Deliverables || Giveaway plans defined || bgcolor="#39FF14" | At least one giveaway plan has been defined and is in the process of being implemented.
|-
| Publication || M1 release is announced ||
|}

Yocto Project v1.1 Release Criteria

2011-06-07T14:17:41Z

Jnfleisc: /* Yocto Project 1.1 */

The Release Criteria for the various Yocto Project 1.1 releases are below.

= Yocto Project 1.1 =
{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''
|-
| Functional Completion || All M1 features and BSPs are in the build. || bgcolor="#39FF14" | [[File:Schedule-status.PNG]] All desired features are in build. One documentation publishing fix remains. see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for details
|-
| Build and Release (Yocto) || All M1 features can be built with no errors. || bgcolor="#39FF14" | Build pulled in all fixes possible.
|- Working
| Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="#39FF14" | Build pulled in all fixes possible.
|-
| Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor="#39FF14" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW NEW bugs] - 2 unaccepted New bugs for 1.1 M1 [http://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&columnlist=bug_severity%2Cpriority%2Ctarget_milestone%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc&priority=High&query_format=advanced&target_milestone=---&target_milestone=0.9%20M1&target_milestone=0.9%20M2&target_milestone=0.9%20M3&target_milestone=0.9%20M4&target_milestone=0.9.1&target_milestone=0.9.2&target_milestone=1.0%20M1&target_milestone=1.0%20M2&target_milestone=1.0%20M3&target_milestone=1.0%20M4&target_milestone=1.1&target_milestone=1.1%20M1&target_milestone=1.1%20M2&target_milestone=1.1%20M3&target_milestone=1.1%20M4&target_milestone=Q1&target_milestone=Q2&target_milestone=Q3&target_milestone=Q4&query_based_on= HIGH priority bugs] - no HIGH priority bugs for 1.1 M1 See trend chart at https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="#39FF14" | [[File:M1.PNG]]
|-
| Distros Tested || Fedora, Ubuntu, Opensuse || bgcolor="#39FF14" | Fedora 14, Ubuntu 11.04, Opensuse 11.4
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="#39FF14" | [[File:M1.PNG]]
|-
| Documentation || M1 documentation deliverables are complete. || bgcolor="#39FF14" | Only deliverable is allowing documentation to be updated even after code freeze. On-track.
|-
| Build Performance || Plan for improving performance is defined. || bgcolor="#39FF14" | Performance goals for M1 (mostly planning goals) were met. See schedule for details. Build is at 102 minutes.
|-
| Upstream Commits || Have upstream status updated on 90% of patches (so that we can have a status update) || bgcolor="#39FF14" | At 85%, which is good enough for alpha.
|-
| Marketing Deliverables || Giveaway plans defined || bgcolor="#39FF14" | At least one giveaway plan has been defined and is in the process of being implemented.
|-
| Publication || M1 release is announced ||
|}

File:M1.PNG

2011-06-07T14:14:26Z

Jnfleisc:

Yocto 1.1 Schedule

2011-05-31T17:26:26Z

Jnfleisc: /* M3 Release (Aug 8 to Aug 15) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| init scripts||provide an image/recipe skeleton as a canonical example||3||Done||RP Notes||WR Distro Team/Robert||M1, Sprint B; Owner: WR Distro Team
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Done||Meta-data||Saul||M1, Sprint C - at 85% in master
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Done||Team||Saul (Dexuan)||M1, Sprint C - bug 1012
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Done||from 1.0||Josh||M1 Sprint D - RFP Sent
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Done||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Done||Meta-data||Mark||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Done||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||Done||Nitin||Nitin||M1, Sprint D
|- style="background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||24-May||Beth||Beth/Scott||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Done||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged on autobuilder site
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||M2, Design||from 1.0||Richard||M2, Design
|}

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||M2, Sprint A||Meta-data||Saul (Edwin)||M2, Sprint A - will reassess if we want to do this
|-
| Package reporting system enhancement||http://packages.yoctoproject.org||2||on-going||Meta-data||Saul (Lei)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||M2, Sprint A||RP Notes||Jessica||M2, Sprint A - under review
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| User Creation at preinstall - complete||Deliverable completed||1||M2, Sprint A||RP Notes||Mark (ScottG)||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||M2, Sprint A||Darren||Darren||M2, Sprint A
|-
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||M2, Sprint A||Rahul||Tom||M2, Sprint A - Tom is submitting patch 24-May. Will go into M2.
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||M2, Sprint A||ADT Team||Jessica||M2, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Disk Space Reduction||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Share gcc work directories||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| multi-lib RPM||RPM support for multilib added||1||M2, Sprint B||from 1.0||Richard (Qing)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||M2, Sprint B||from 1.0||Tom||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint D
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|-
| Share gcc work directories||||2||Accept||Team||WR Distro Team||M2, Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged on autobuilder site
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged on autobuilder site
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-31T17:26:13Z

Jnfleisc: /* M2 Release (July 18 to July 22) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| init scripts||provide an image/recipe skeleton as a canonical example||3||Done||RP Notes||WR Distro Team/Robert||M1, Sprint B; Owner: WR Distro Team
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Done||Meta-data||Saul||M1, Sprint C - at 85% in master
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Done||Team||Saul (Dexuan)||M1, Sprint C - bug 1012
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Done||from 1.0||Josh||M1 Sprint D - RFP Sent
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Done||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Done||Meta-data||Mark||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Done||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||Done||Nitin||Nitin||M1, Sprint D
|- style="background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||24-May||Beth||Beth/Scott||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Done||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged on autobuilder site
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||M2, Design||from 1.0||Richard||M2, Design
|}

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||M2, Sprint A||Meta-data||Saul (Edwin)||M2, Sprint A - will reassess if we want to do this
|-
| Package reporting system enhancement||http://packages.yoctoproject.org||2||on-going||Meta-data||Saul (Lei)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||M2, Sprint A||RP Notes||Jessica||M2, Sprint A - under review
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| User Creation at preinstall - complete||Deliverable completed||1||M2, Sprint A||RP Notes||Mark (ScottG)||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||M2, Sprint A||Darren||Darren||M2, Sprint A
|-
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||M2, Sprint A||Rahul||Tom||M2, Sprint A - Tom is submitting patch 24-May. Will go into M2.
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||M2, Sprint A||ADT Team||Jessica||M2, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Disk Space Reduction||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Share gcc work directories||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| multi-lib RPM||RPM support for multilib added||1||M2, Sprint B||from 1.0||Richard (Qing)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||M2, Sprint B||from 1.0||Tom||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint D
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|-
| Share gcc work directories||||2||Accept||Team||WR Distro Team||M2, Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged on autobuilder site
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-31T17:25:48Z

Jnfleisc: /* M1 Release (June 6 to June 13) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| init scripts||provide an image/recipe skeleton as a canonical example||3||Done||RP Notes||WR Distro Team/Robert||M1, Sprint B; Owner: WR Distro Team
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Done||Meta-data||Saul||M1, Sprint C - at 85% in master
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Done||Team||Saul (Dexuan)||M1, Sprint C - bug 1012
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Done||from 1.0||Josh||M1 Sprint D - RFP Sent
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Done||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Done||Meta-data||Mark||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Done||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||Done||Nitin||Nitin||M1, Sprint D
|- style="background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||24-May||Beth||Beth/Scott||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Done||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged on autobuilder site
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||M2, Design||from 1.0||Richard||M2, Design
|}

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||M2, Sprint A||Meta-data||Saul (Edwin)||M2, Sprint A - will reassess if we want to do this
|-
| Package reporting system enhancement||http://packages.yoctoproject.org||2||on-going||Meta-data||Saul (Lei)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||M2, Sprint A||RP Notes||Jessica||M2, Sprint A - under review
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| User Creation at preinstall - complete||Deliverable completed||1||M2, Sprint A||RP Notes||Mark (ScottG)||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||M2, Sprint A||Darren||Darren||M2, Sprint A
|-
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||M2, Sprint A||Rahul||Tom||M2, Sprint A - Tom is submitting patch 24-May. Will go into M2.
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||M2, Sprint A||ADT Team||Jessica||M2, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Disk Space Reduction||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Share gcc work directories||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| multi-lib RPM||RPM support for multilib added||1||M2, Sprint B||from 1.0||Richard (Qing)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||M2, Sprint B||from 1.0||Tom||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint D
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|-
| Share gcc work directories||||2||Accept||Team||WR Distro Team||M2, Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto Project v1.1 Release Criteria

2011-05-31T15:45:14Z

Jnfleisc: /* Yocto Project 1.1 */ added 31-May status

The Release Criteria for the various Yocto Project 1.1 releases are below.

= Yocto Project 1.1 =
{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''
|-
| Functional Completion || All M1 features and BSPs are in the build. || bgcolor="#39FF14" | [[File:Schedule-status.PNG]] All desired features are in build. One documentation publishing fix remains. see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for details
|-
| Build and Release (Yocto) || All M1 features can be built with no errors. || bgcolor="#39FF14" | Build pulled in all fixes possible.
|- Working
| Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="#39FF14" | Build pulled in all fixes possible.
|-
| Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor="#39FF14" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW NEW bugs] - 2 unaccepted New bugs for 1.1 M1 [http://bugzilla.yoctoproject.org/buglist.cgi?priority=High&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=---&target_milestone=0.9%20M1&target_milestone=0.9%20M2&target_milestone=0.9%20M3&target_milestone=0.9%20M4&target_milestone=0.9.1&target_milestone=0.9.2&target_milestone=1.0%20M1&target_milestone=1.0%20M2&target_milestone=1.0%20M3&target_milestone=1.0%20M4&target_milestone=1.1&target_milestone=1.1%20M1&target_milestone=1.1%20M2&target_milestone=1.1%20M3&target_milestone=1.1%20M4&target_milestone=Q1&target_milestone=Q2&target_milestone=Q3&target_milestone=Q4 HIGH priority bugs] - no HIGH priority bugs for 1.1 M1 See trend chart at https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="yellow" | Test pass in progress
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="yellow" | Test pass in progress
|-
| Documentation || M1 documentation deliverables are complete. || bgcolor="#39FF14" | Only deliverable is allowing documentation to be updated even after code freeze. On-track.
|-
| Build Performance || Plan for improving performance is defined. || bgcolor="#39FF14" | Performance goals for M1 (mostly planning goals) were met. See schedule for details. Build is at 102 minutes.
|-
| Upstream Commits || Have upstream status updated on 90% of patches (so that we can have a status update) || bgcolor="#39FF14" | At 85%, which is good enough for alpha.
|-
| Marketing Deliverables || Giveaway plans defined || bgcolor="#39FF14" | At least one giveaway plan has been defined and is in the process of being implemented.
|-
| Publication || M1 release is announced ||
|}

Yocto Project v1.1 Release Criteria

2011-05-25T14:31:22Z

Jnfleisc: /* Yocto Project 1.1 */ added 24-May status

The Release Criteria for the various Yocto Project 1.1 releases are below.

= Yocto Project 1.1 =
{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''
|-
| Functional Completion || All M1 features and BSPs are in the build. || bgcolor="#39FF14" | [[File:Schedule-status.PNG]] All desired features are in build. One documentation publishing fix remains. see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for details
|-
| Build and Release (Yocto) || All M1 features can be built with no errors. || bgcolor="orange" | QEMU build, but full build did not complete. QA is starting a partial test pass on what built.
|- Working
| Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="orange" | Crown Bay EMGD had some issues.
|-
| Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor="yellow" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW NEW bugs] - 3 unaccepted New bugs for 1.1 M1 [http://bugzilla.yoctoproject.org/buglist.cgi?priority=High&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=---&target_milestone=0.9%20M1&target_milestone=0.9%20M2&target_milestone=0.9%20M3&target_milestone=0.9%20M4&target_milestone=0.9.1&target_milestone=0.9.2&target_milestone=1.0%20M1&target_milestone=1.0%20M2&target_milestone=1.0%20M3&target_milestone=1.0%20M4&target_milestone=1.1&target_milestone=1.1%20M1&target_milestone=1.1%20M2&target_milestone=1.1%20M3&target_milestone=1.1%20M4&target_milestone=Q1&target_milestone=Q2&target_milestone=Q3&target_milestone=Q4 HIGH priority bugs] - no HIGH priority bugs for 1.1 M1 See trend chart at https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | QA can only do weekly test pass. Will begin full test pass when build completes.
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | QA can only do weekly test pass. Will begin full test pass when build completes.
|-
| Documentation || M1 documentation deliverables are complete. || bgcolor="#39FF14" | Only deliverable is allowing documentation to be updated even after code freeze. On-track.
|-
| Build Performance || Plan for improving performance is defined. || bgcolor="#39FF14" | Performance goals for M1 (mostly planning goals) were met. See schedule for details.
|-
| Upstream Commits || Have upstream status updated on 90% of patches (so that we can have a status update) || bgcolor="#39FF14" | At 85%, which is good enough for alpha.
|-
| Marketing Deliverables || Giveaway plans defined || bgcolor="#39FF14" | At least one giveaway plan has been defined and is in the process of being implemented.
|-
| Publication || M1 release is announced ||
|}

File:Schedule-status.PNG

2011-05-25T14:23:47Z

Jnfleisc: uploaded a new version of "File:Schedule-status.PNG"

Yocto 1.1 Schedule

2011-05-25T14:21:09Z

Jnfleisc: /* M2 Sprint B (June 13 to June 17) */ added 24-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Done||Meta-data||Saul||M1, Sprint C - at 85% in master
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Done||Team||Saul (Dexuan)||M1, Sprint C - bug 1012
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Done||from 1.0||Josh||M1 Sprint D - RFP Sent
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Done||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Done||Meta-data||Mark||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Done||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||Done||Nitin||Nitin||M1, Sprint D
|- style="background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||24-May||Beth||Beth/Scott||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Done||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||M2, Design||from 1.0||Richard||M2, Design
|}

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||M2, Sprint A||Meta-data||Saul (Edwin)||M2, Sprint A - will reassess if we want to do this
|-
| Package reporting system enhancement||http://packages.yoctoproject.org||2||on-going||Meta-data||Saul (Lei)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||M2, Sprint A||RP Notes||Jessica||M2, Sprint A - under review
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| User Creation at preinstall - complete||Deliverable completed||1||M2, Sprint A||RP Notes||Mark (ScottG)||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||M2, Sprint A||Darren||Darren||M2, Sprint A
|-
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||M2, Sprint A||Rahul||Tom||M2, Sprint A - Tom is submitting patch 24-May. Will go into M2.
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||M2, Sprint A||ADT Team||Jessica||M2, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Disk Space Reduction||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Share gcc work directories||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| multi-lib RPM||RPM support for multilib added||1||M2, Sprint B||from 1.0||Richard (Qing)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||M2, Sprint B||from 1.0||Tom||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-25T14:20:14Z

Jnfleisc: /* M2 Design (May 30 to June 3) */ added 24-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Done||Meta-data||Saul||M1, Sprint C - at 85% in master
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Done||Team||Saul (Dexuan)||M1, Sprint C - bug 1012
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Done||from 1.0||Josh||M1 Sprint D - RFP Sent
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Done||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Done||Meta-data||Mark||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Done||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||Done||Nitin||Nitin||M1, Sprint D
|- style="background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||24-May||Beth||Beth/Scott||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Done||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||M2, Design||from 1.0||Richard||M2, Design
|}

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||M2, Sprint A||Meta-data||Saul (Edwin)||M2, Sprint A - will reassess if we want to do this
|-
| Package reporting system enhancement||http://packages.yoctoproject.org||2||on-going||Meta-data||Saul (Lei)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||M2, Sprint A||RP Notes||Jessica||M2, Sprint A - under review
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| User Creation at preinstall - complete||Deliverable completed||1||M2, Sprint A||RP Notes||Mark (ScottG)||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||M2, Sprint A||Darren||Darren||M2, Sprint A
|-
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||M2, Sprint A||Rahul||Tom||M2, Sprint A - Tom is submitting patch 24-May. Will go into M2.
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||M2, Sprint A||ADT Team||Jessica||M2, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Disk Space Reduction||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Share gcc work directories||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-25T14:19:02Z

Jnfleisc: /* M2 Sprint A (June 6 to June 10) */ added 24-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Done||Meta-data||Saul||M1, Sprint C - at 85% in master
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Done||Team||Saul (Dexuan)||M1, Sprint C - bug 1012
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Done||from 1.0||Josh||M1 Sprint D - RFP Sent
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Done||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Done||Meta-data||Mark||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Done||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||Done||Nitin||Nitin||M1, Sprint D
|- style="background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||24-May||Beth||Beth/Scott||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Done||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||M2, Sprint A||Meta-data||Saul (Edwin)||M2, Sprint A - will reassess if we want to do this
|-
| Package reporting system enhancement||http://packages.yoctoproject.org||2||on-going||Meta-data||Saul (Lei)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||M2, Sprint A||RP Notes||Jessica||M2, Sprint A - under review
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| User Creation at preinstall - complete||Deliverable completed||1||M2, Sprint A||RP Notes||Mark (ScottG)||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||M2, Sprint A||Darren||Darren||M2, Sprint A
|-
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||M2, Sprint A||Rahul||Tom||M2, Sprint A - Tom is submitting patch 24-May. Will go into M2.
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||M2, Sprint A||ADT Team||Jessica||M2, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Disk Space Reduction||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Share gcc work directories||||2||M2, Sprint A||Team||WR Distro Team||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||M2, Sprint A||Tom||Tom||M2, Sprint A
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-25T14:16:45Z

Jnfleisc: /* M1 Stabilize (May 23 to June 3) */ added 24-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Done||Meta-data||Saul||M1, Sprint C - at 85% in master
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Done||Team||Saul (Dexuan)||M1, Sprint C - bug 1012
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Done||from 1.0||Josh||M1 Sprint D - RFP Sent
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Done||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Done||Meta-data||Mark||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Done||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||Done||Nitin||Nitin||M1, Sprint D
|- style="background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||24-May||Beth||Beth/Scott||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Done||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-25T14:14:21Z

Jnfleisc: /* M1 Sprint D (May 16 to May 20) */ added 24-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Done||Meta-data||Saul||M1, Sprint C - at 85% in master
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Done||Team||Saul (Dexuan)||M1, Sprint C - bug 1012
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Done||from 1.0||Josh||M1 Sprint D - RFP Sent
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Done||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Done||Meta-data||Mark||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Done||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||Done||Nitin||Nitin||M1, Sprint D
|- style="background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||24-May||Beth||Beth/Scott||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-25T14:13:11Z

Jnfleisc: /* M1 Sprint C (May 9 to May 13) */ added 24-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Done||Meta-data||Saul||M1, Sprint C - at 85% in master
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Done||Team||Saul (Dexuan)||M1, Sprint C - bug 1012
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style = "background:yellow"
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|- style = "background:yellow"
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D - may be removed
|- style = "background:yellow"
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||20-May||from 1.0||Josh||M1 Sprint D
|- style = "background:yellow"
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||20-May||Meta-data||Saul (Edwin)||M1, Sprint D
|- style = "background:yellow"
| Package reporting system enhancement||||2||20-May||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|- style = "background:yellow"
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||on-going||Meta-data||WR Distro Team||M1, Sprint D
|- style = "background:orange"
| 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||23-May||Meta-data||Mark||M1, Sprint D
|- style = "background:yellow"
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||20-May||RP Notes||Jessica||M1, Sprint D
|-style = "background:yellow"
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||20-May||RP Notes||Saul (Nitin)||M1, Sprint D
|- style = "background:yellow"
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||19-May||Nitin||Nitin||M1, Sprint D
|- style = "background:yellow"
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||20-May||Tom||Tom||M1, Sprint D - development done, needs to be pulled into kernel. Also, testing needs to be done.
|- style = "background:yellow"
| BBXM||Pull in bits from OE (kernel and uboot)||1||20-May||Darren||Darren||M1, Sprint D - uboot for May 20th; kernel may slip to M2
|- style = "background:yellow"
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||20-May||ADT Team||Jessica||M1, Sprint D - need Richard\'s review to finish
|- style = "background:yellow"
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||20-May||Beth||Beth/Scott||M1, Sprint D
|- style = "background:yellow"
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||20-May||from 1.0||Tom||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-25T00:59:49Z

Jnfleisc: /* M1 Sprint A (Apr 25 to Apr 29) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:orange"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||20-May||from 1.0||Richard||M1, Sprint C
|- style="background:orange"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||20-May||Meta-data||Saul||M1, Sprint C - at 75% in master, have 10-15% more
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|- style="background:orange"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||20-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:orange"
| User Creation at preinstall - complete||Deliverable completed||1||18-May||RP Notes||Mark (ScottG)||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|- style="background:orange"
| Disk Space Reduction||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|- style="background:orange"
| Share gcc work directories||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:orange"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||20-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style = "background:yellow"
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|- style = "background:yellow"
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D - may be removed
|- style = "background:yellow"
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||20-May||from 1.0||Josh||M1 Sprint D
|- style = "background:yellow"
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||20-May||Meta-data||Saul (Edwin)||M1, Sprint D
|- style = "background:yellow"
| Package reporting system enhancement||||2||20-May||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|- style = "background:yellow"
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||on-going||Meta-data||WR Distro Team||M1, Sprint D
|- style = "background:orange"
| 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||23-May||Meta-data||Mark||M1, Sprint D
|- style = "background:yellow"
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||20-May||RP Notes||Jessica||M1, Sprint D
|-style = "background:yellow"
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||20-May||RP Notes||Saul (Nitin)||M1, Sprint D
|- style = "background:yellow"
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||19-May||Nitin||Nitin||M1, Sprint D
|- style = "background:yellow"
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||20-May||Tom||Tom||M1, Sprint D - development done, needs to be pulled into kernel. Also, testing needs to be done.
|- style = "background:yellow"
| BBXM||Pull in bits from OE (kernel and uboot)||1||20-May||Darren||Darren||M1, Sprint D - uboot for May 20th; kernel may slip to M2
|- style = "background:yellow"
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||20-May||ADT Team||Jessica||M1, Sprint D - need Richard\'s review to finish
|- style = "background:yellow"
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||20-May||Beth||Beth/Scott||M1, Sprint D
|- style = "background:yellow"
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||20-May||from 1.0||Tom||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto Project v1.0.1 Release Criteria

2011-05-24T19:07:13Z

Jnfleisc: /* Yocto Project 1.0.1 Release Criteria */ added 24-May status

== Yocto Project 1.0.1 Release Criteria ==
Yocto Project 1.0.1 is a point release from Yocto Project 1.0. In general, it contains critical bug fixes as well as nice to have items that are small, well-contained and provide a high benefit to include.

The criteria for adding a code submission into 1.0.1 are that the change:
* Addresses a High priority issue. (Typically, these have critical or major severity.)
* Is small and simple to evaluate (both in lines of code and complexity)
* Fixes a specific problem which users are likely to encounter
* Fixes that problem in a clearly defined way
* Is self contained and unlikely to interact badly with other parts of the system
* Fixes known/clear bugs

Good candidate changes are ones which:
* Address usability issues
* Address host specific issues, particularly in releases of distros that come out after our release
* Address post release bugs users are hitting and reporting
* Address security issues

Bad candidate changes include:
* Significant changes of version (point release for security problems are acceptable)
* Anything involves major code changes where changes cannot be reviewed individually or separated out
* Adding new features
* Changes that break the layout or compatibility with existing builds
* Changes that would trigger significant rebuilds

{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Target''' || ! scope="col" bgcolor="grey" | '''Status'''
|-
| Functional Completion || No new significant features are added. Any minor functionality added is documented in git logs. || bgcolor="#39FF14" | List of commits has been defined and reviewed and all bugs are in the release.
|-
| Build and Release (Yocto) || 1.0.1 build can be built with no errors. || bgcolor="#39FF14" | Build was successful.
|-
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || N/A - BSPs will not be built for 1.0.1.
|-
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="#39FF14" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.0%20PointRelease Open bug query] shows one bug - not a show-stopper? Bugs found during testing have been fixed: [http://bugzilla.pokylinux.org/show_bug.cgi?id=1029 bug 1029] Fixed - mmc commands must be run from a prompt to do uboot - this will go in Release Notes and README.hardware [http://bugzilla.pokylinux.org/show_bug.cgi?id=1087 bug 1087] is Fixed Total bug count: [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.0%20PointRelease 28 bugs total]
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="#39FF14" | BLOCKED items are now tested [[file:1.0.1FullTest_Pass19MAY11.PNG]] Compliance tests will not be done for 1.0.1.
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="#39FF14" | Tests passed
|-
| Documentation || 1.0.1 Release Notes are complete. || bgcolor="yellow" | Need to provide Release Notes to tech editor prior to release.
|-
| Build Performance || 1.0.1 does not increase performance above 107 minutes on a developer machine. || bgcolor="yellow" | We have increased build time (~2 minutes) due to a fix, but this was a concsious decision by the team.
|-
| Publication || 1.0.1 release is built and announced to the community. ||
|}

Yocto 1.1 Schedule

2011-05-19T22:31:48Z

Jnfleisc: /* M3 Design (Jul 11 to Jul 15) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||20-May||Rahul||Tom||M1, Sprint A - met with team; will finalize configuration this week and complete
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:orange"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||20-May||from 1.0||Richard||M1, Sprint C
|- style="background:orange"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||20-May||Meta-data||Saul||M1, Sprint C - at 75% in master, have 10-15% more
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|- style="background:orange"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||20-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:orange"
| User Creation at preinstall - complete||Deliverable completed||1||18-May||RP Notes||Mark (ScottG)||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|- style="background:orange"
| Disk Space Reduction||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|- style="background:orange"
| Share gcc work directories||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:orange"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||20-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style = "background:yellow"
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|- style = "background:yellow"
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D - may be removed
|- style = "background:yellow"
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||20-May||from 1.0||Josh||M1 Sprint D
|- style = "background:yellow"
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||20-May||Meta-data||Saul (Edwin)||M1, Sprint D
|- style = "background:yellow"
| Package reporting system enhancement||||2||20-May||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|- style = "background:yellow"
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||on-going||Meta-data||WR Distro Team||M1, Sprint D
|- style = "background:orange"
| 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||23-May||Meta-data||Mark||M1, Sprint D
|- style = "background:yellow"
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||20-May||RP Notes||Jessica||M1, Sprint D
|-style = "background:yellow"
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||20-May||RP Notes||Saul (Nitin)||M1, Sprint D
|- style = "background:yellow"
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||19-May||Nitin||Nitin||M1, Sprint D
|- style = "background:yellow"
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||20-May||Tom||Tom||M1, Sprint D - development done, needs to be pulled into kernel. Also, testing needs to be done.
|- style = "background:yellow"
| BBXM||Pull in bits from OE (kernel and uboot)||1||20-May||Darren||Darren||M1, Sprint D - uboot for May 20th; kernel may slip to M2
|- style = "background:yellow"
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||20-May||ADT Team||Jessica||M1, Sprint D - need Richard\'s review to finish
|- style = "background:yellow"
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||20-May||Beth||Beth/Scott||M1, Sprint D
|- style = "background:yellow"
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||20-May||from 1.0||Tom||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Scott G (Robert)||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-19T22:30:58Z

Jnfleisc: /* M2 Sprint D (June 27 to July 1) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||20-May||Rahul||Tom||M1, Sprint A - met with team; will finalize configuration this week and complete
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:orange"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||20-May||from 1.0||Richard||M1, Sprint C
|- style="background:orange"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||20-May||Meta-data||Saul||M1, Sprint C - at 75% in master, have 10-15% more
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|- style="background:orange"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||20-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:orange"
| User Creation at preinstall - complete||Deliverable completed||1||18-May||RP Notes||Mark (ScottG)||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|- style="background:orange"
| Disk Space Reduction||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|- style="background:orange"
| Share gcc work directories||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:orange"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||20-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style = "background:yellow"
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|- style = "background:yellow"
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D - may be removed
|- style = "background:yellow"
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||20-May||from 1.0||Josh||M1 Sprint D
|- style = "background:yellow"
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||20-May||Meta-data||Saul (Edwin)||M1, Sprint D
|- style = "background:yellow"
| Package reporting system enhancement||||2||20-May||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|- style = "background:yellow"
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||on-going||Meta-data||WR Distro Team||M1, Sprint D
|- style = "background:orange"
| 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||23-May||Meta-data||Mark||M1, Sprint D
|- style = "background:yellow"
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||20-May||RP Notes||Jessica||M1, Sprint D
|-style = "background:yellow"
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||20-May||RP Notes||Saul (Nitin)||M1, Sprint D
|- style = "background:yellow"
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||19-May||Nitin||Nitin||M1, Sprint D
|- style = "background:yellow"
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||20-May||Tom||Tom||M1, Sprint D - development done, needs to be pulled into kernel. Also, testing needs to be done.
|- style = "background:yellow"
| BBXM||Pull in bits from OE (kernel and uboot)||1||20-May||Darren||Darren||M1, Sprint D - uboot for May 20th; kernel may slip to M2
|- style = "background:yellow"
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||20-May||ADT Team||Jessica||M1, Sprint D - need Richard\'s review to finish
|- style = "background:yellow"
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||20-May||Beth||Beth/Scott||M1, Sprint D
|- style = "background:yellow"
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||20-May||from 1.0||Tom||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-19T22:30:35Z

Jnfleisc: /* M2 Sprint C (June 20 to June 24) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||20-May||Rahul||Tom||M1, Sprint A - met with team; will finalize configuration this week and complete
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:orange"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||20-May||from 1.0||Richard||M1, Sprint C
|- style="background:orange"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||20-May||Meta-data||Saul||M1, Sprint C - at 75% in master, have 10-15% more
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|- style="background:orange"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||20-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:orange"
| User Creation at preinstall - complete||Deliverable completed||1||18-May||RP Notes||Mark (ScottG)||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|- style="background:orange"
| Disk Space Reduction||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|- style="background:orange"
| Share gcc work directories||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:orange"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||20-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style = "background:yellow"
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|- style = "background:yellow"
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D - may be removed
|- style = "background:yellow"
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||20-May||from 1.0||Josh||M1 Sprint D
|- style = "background:yellow"
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||20-May||Meta-data||Saul (Edwin)||M1, Sprint D
|- style = "background:yellow"
| Package reporting system enhancement||||2||20-May||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|- style = "background:yellow"
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||on-going||Meta-data||WR Distro Team||M1, Sprint D
|- style = "background:orange"
| 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||23-May||Meta-data||Mark||M1, Sprint D
|- style = "background:yellow"
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||20-May||RP Notes||Jessica||M1, Sprint D
|-style = "background:yellow"
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||20-May||RP Notes||Saul (Nitin)||M1, Sprint D
|- style = "background:yellow"
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||19-May||Nitin||Nitin||M1, Sprint D
|- style = "background:yellow"
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||20-May||Tom||Tom||M1, Sprint D - development done, needs to be pulled into kernel. Also, testing needs to be done.
|- style = "background:yellow"
| BBXM||Pull in bits from OE (kernel and uboot)||1||20-May||Darren||Darren||M1, Sprint D - uboot for May 20th; kernel may slip to M2
|- style = "background:yellow"
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||20-May||ADT Team||Jessica||M1, Sprint D - need Richard\'s review to finish
|- style = "background:yellow"
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||20-May||Beth||Beth/Scott||M1, Sprint D
|- style = "background:yellow"
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||20-May||from 1.0||Tom||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Scott G (Robert)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

File:1.0.1FullTest Pass19MAY11.PNG

2011-05-19T14:46:13Z

Jnfleisc:

Yocto Project v1.0.1 Release Criteria

2011-05-19T14:23:24Z

Jnfleisc: /* Yocto Project 1.0.1 Release Criteria */ added 19-May status

== Yocto Project 1.0.1 Release Criteria ==
Yocto Project 1.0.1 is a point release from Yocto Project 1.0. In general, it contains critical bug fixes as well as nice to have items that are small, well-contained and provide a high benefit to include.

The criteria for adding a code submission into 1.0.1 are that the change:
* Addresses a High priority issue. (Typically, these have critical or major severity.)
* Is small and simple to evaluate (both in lines of code and complexity)
* Fixes a specific problem which users are likely to encounter
* Fixes that problem in a clearly defined way
* Is self contained and unlikely to interact badly with other parts of the system
* Fixes known/clear bugs

Good candidate changes are ones which:
* Address usability issues
* Address host specific issues, particularly in releases of distros that come out after our release
* Address post release bugs users are hitting and reporting
* Address security issues

Bad candidate changes include:
* Significant changes of version (point release for security problems are acceptable)
* Anything involves major code changes where changes cannot be reviewed individually or separated out
* Adding new features
* Changes that break the layout or compatibility with existing builds
* Changes that would trigger significant rebuilds

{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Target''' || ! scope="col" bgcolor="grey" | '''Status'''
|-
| Functional Completion || No new significant features are added. Any minor functionality added is documented in git logs. || bgcolor="#39FF14" | List of commits has been defined and reviewed and all bugs are in the release.
|-
| Build and Release (Yocto) || 1.0.1 build can be built with no errors. || bgcolor="#39FF14" | Build was successful.
|-
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || N/A - BSPs will not be built for 1.0.1.
|-
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="red" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.0%20PointRelease Open bug query] shows one bug - not a show-stopper? New bugs found during testing: [http://bugzilla.pokylinux.org/show_bug.cgi?id=1029 bug 1029] exists for 1.0.1 - Is this a regression from 1.0? [http://bugzilla.pokylinux.org/show_bug.cgi?id=1087 bug 1087] was just found Total bug count: [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.0%20PointRelease 39 bugs total]
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="yellow" | [[file:1.0.1FullTest_Pass19MAY11.PNG]] Compliance tests will not be done for 1.0.1.
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="red" | WEEKLY TESTING ONLY was done. See above for high level status. Two bugs: [http://bugzilla.pokylinux.org/show_bug.cgi?id=1029 bug 1029]: Beagleboard cannot boot up from uboot [http://bugzilla.pokylinux.org/show_bug.cgi?id=1087 bug 1087]: libzypp fails to do_compile for crownbay
|-
| Documentation || 1.0.1 Release Notes are complete. || bgcolor="orange" | Need to provide Release Notes to tech editor prior to release.
|-
| Build Performance || 1.0.1 does not increase performance above 107 minutes on a developer machine. || bgcolor="yellow" | We have increased build time (~2 minutes) due to a fix, but this was a concsious decision by the team.
|-
| Publication || 1.0.1 release is built and announced to the community. ||
|}

Yocto Project v1.0.1 Release Criteria

2011-05-18T15:04:58Z

Jnfleisc: /* Yocto Project 1.0.1 Release Criteria */

== Yocto Project 1.0.1 Release Criteria ==
Yocto Project 1.0.1 is a point release from Yocto Project 1.0. In general, it contains critical bug fixes as well as nice to have items that are small, well-contained and provide a high benefit to include.

The criteria for adding a code submission into 1.0.1 are that the change:
* Addresses a High priority issue. (Typically, these have critical or major severity.)
* Is small and simple to evaluate (both in lines of code and complexity)
* Fixes a specific problem which users are likely to encounter
* Fixes that problem in a clearly defined way
* Is self contained and unlikely to interact badly with other parts of the system
* Fixes known/clear bugs

Good candidate changes are ones which:
* Address usability issues
* Address host specific issues, particularly in releases of distros that come out after our release
* Address post release bugs users are hitting and reporting
* Address security issues

Bad candidate changes include:
* Significant changes of version (point release for security problems are acceptable)
* Anything involves major code changes where changes cannot be reviewed individually or separated out
* Adding new features
* Changes that break the layout or compatibility with existing builds
* Changes that would trigger significant rebuilds

{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Target''' || ! scope="col" bgcolor="grey" | '''Status'''
|-
| Functional Completion || No new significant features are added. Any minor functionality added is documented in git logs. || bgcolor="#39FF14" | List of commits has been defined and reviewed and all bugs are in the release.
|-
| Build and Release (Yocto) || 1.0.1 build can be built with no errors. || bgcolor="#39FF14" | Build was successful.
|-
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || N/A - BSPs will not be built for 1.0.1.
|-
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="red" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.0%20PointRelease 1 bug] exists for 1.0.1 - not a show-stopper? [http://bugzilla.pokylinux.org/show_bug.cgi?id=1029 bug 1029] exists for 1.0.1 - If this is a regression from 1.0, then it needs to be fixed. We will continue with a full QA test pass and meet on the 19th to discuss status. If this issue is addressed, a full test pass may not need to be needed after fixing. [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.0%20PointRelease 39 bugs total]
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | Full test pass May 13-18. Results posted for go/no-go on 19th. Compliance tests will not be done for 1.0.1. preliminary results available - bug 1029 exists in 1.0.1
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="yellow" | BSPs will have a weekly test pass for 1.0.1.
|-
| Documentation || 1.0.1 Release Notes are complete. || bgcolor="yellow" | Release notes will include high priority bugs fixed, pointer to bugzilla, security advisories.
|-
| Build Performance || 1.0.1 does not increase performance above 107 minutes on a developer machine. || bgcolor="yellow" | We have increased build time (~2 minutes) due to a fix, but this was a concsious decision by the team.
|-
| Publication || 1.0.1 release is built and announced to the community. ||
|}

Yocto Project v1.1 Release Criteria

2011-05-18T15:00:00Z

Jnfleisc: /* Yocto Project 1.1 */

The Release Criteria for the various Yocto Project 1.1 releases are below.

= Yocto Project 1.1 =
{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''
|-
| Functional Completion || All M1 features and BSPs are in the build. || bgcolor="yellow" | [[File:Schedule-status.PNG]] see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for details
|-
| Build and Release (Yocto) || All M1 features can be built with no errors. || bgcolor="yellow" | Build is currently working.
|- Working
| Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="orange" | BSP builds are blocked.
|-
| Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor="orange" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW NEW bugs] [http://bugzilla.yoctoproject.org/buglist.cgi?priority=High&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=---&target_milestone=0.9%20M1&target_milestone=0.9%20M2&target_milestone=0.9%20M3&target_milestone=0.9%20M4&target_milestone=0.9.1&target_milestone=0.9.2&target_milestone=1.0%20M1&target_milestone=1.0%20M2&target_milestone=1.0%20M3&target_milestone=1.0%20M4&target_milestone=1.1&target_milestone=1.1%20M1&target_milestone=1.1%20M2&target_milestone=1.1%20M3&target_milestone=1.1%20M4&target_milestone=Q1&target_milestone=Q2&target_milestone=Q3&target_milestone=Q4 HIGH priority bugs] Ke will check with Qing on status of 1030
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | See email for details. All features buggy.
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | See email for details. BSPs are blocked.
|-
| Documentation || M1 documentation deliverables are complete. || bgcolor="#39FF14" | Only deliverable is allowing documentation to be updated even after code freeze. On-track.
|-
| Build Performance || Plan for improving performance is defined. || bgcolor="yellow" | See schedule for details.
|-
| Upstream Commits || Have upstream status updated on 90% of patches (so that we can have a status update) || bgcolor="yellow" | Nearing 90% goal.
|-
| Marketing Deliverables || Giveaway plans defined || bgcolor="yellow" | Julie, Jefro, Darren, Tracey are working on a giveaway plan.
|-
| Publication || M1 release is announced ||
|}

Yocto Project v1.1 Release Criteria

2011-05-18T14:58:22Z

Jnfleisc: /* Yocto Project 1.1 */ added 17-May status

The Release Criteria for the various Yocto Project 1.1 releases are below.

= Yocto Project 1.1 =
{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''
|-
| Functional Completion || All M1 features and BSPs are in the build. || bgcolor="yellow" | [[File:Schedule-status.PNG]] see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for details
|-
| Build and Release (Yocto) || All M1 features can be built with no errors. || bgcolor="yellow" | Build is currently working.
|- Working
| Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="yellow" | Build is currently working.
|-
| Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor="orange" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW NEW bugs] [http://bugzilla.yoctoproject.org/buglist.cgi?priority=High&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=---&target_milestone=0.9%20M1&target_milestone=0.9%20M2&target_milestone=0.9%20M3&target_milestone=0.9%20M4&target_milestone=0.9.1&target_milestone=0.9.2&target_milestone=1.0%20M1&target_milestone=1.0%20M2&target_milestone=1.0%20M3&target_milestone=1.0%20M4&target_milestone=1.1&target_milestone=1.1%20M1&target_milestone=1.1%20M2&target_milestone=1.1%20M3&target_milestone=1.1%20M4&target_milestone=Q1&target_milestone=Q2&target_milestone=Q3&target_milestone=Q4 HIGH priority bugs] Ke will check with Qing on status of 1030
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | See email for details. All features buggy.
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | See email for details. BSPs are blocked.
|-
| Documentation || M1 documentation deliverables are complete. || bgcolor="#39FF14" | Only deliverable is allowing documentation to be updated even after code freeze. On-track.
|-
| Build Performance || Plan for improving performance is defined. || bgcolor="yellow" | See schedule for details.
|-
| Upstream Commits || Have upstream status updated on 90% of patches (so that we can have a status update) || bgcolor="yellow" | Nearing 90% goal.
|-
| Marketing Deliverables || Giveaway plans defined || bgcolor="yellow" | Julie, Jefro, Darren, Tracey are working on a giveaway plan.
|-
| Publication || M1 release is announced ||
|}

File:Schedule-status.PNG

2011-05-18T14:54:57Z

Jnfleisc:

Yocto 1.1 Schedule

2011-05-18T14:45:50Z

Jnfleisc: /* M2 Sprint D (June 27 to July 1) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||20-May||Rahul||Tom||M1, Sprint A - met with team; will finalize configuration this week and complete
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:orange"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||20-May||from 1.0||Richard||M1, Sprint C
|- style="background:orange"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||20-May||Meta-data||Saul||M1, Sprint C - at 75% in master, have 10-15% more
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|- style="background:orange"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||20-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:orange"
| User Creation at preinstall - complete||Deliverable completed||1||18-May||RP Notes||Mark (ScottG)||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|- style="background:orange"
| Disk Space Reduction||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|- style="background:orange"
| Share gcc work directories||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:orange"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||20-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style = "background:yellow"
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|- style = "background:yellow"
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D - may be removed
|- style = "background:yellow"
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||20-May||from 1.0||Josh||M1 Sprint D
|- style = "background:yellow"
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||20-May||Meta-data||Saul (Edwin)||M1, Sprint D
|- style = "background:yellow"
| Package reporting system enhancement||||2||20-May||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|- style = "background:yellow"
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||on-going||Meta-data||WR Distro Team||M1, Sprint D
|- style = "background:orange"
| 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||23-May||Meta-data||Mark||M1, Sprint D
|- style = "background:yellow"
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||20-May||RP Notes||Jessica||M1, Sprint D
|-style = "background:yellow"
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||20-May||RP Notes||Saul (Nitin)||M1, Sprint D
|- style = "background:yellow"
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||19-May||Nitin||Nitin||M1, Sprint D
|- style = "background:yellow"
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||20-May||Tom||Tom||M1, Sprint D - development done, needs to be pulled into kernel. Also, testing needs to be done.
|- style = "background:yellow"
| BBXM||Pull in bits from OE (kernel and uboot)||1||20-May||Darren||Darren||M1, Sprint D - uboot for May 20th; kernel may slip to M2
|- style = "background:yellow"
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||20-May||ADT Team||Jessica||M1, Sprint D - need Richard\'s review to finish
|- style = "background:yellow"
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||20-May||Beth||Beth/Scott||M1, Sprint D
|- style = "background:yellow"
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||20-May||from 1.0||Tom||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint D
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-18T14:45:31Z

Jnfleisc: /* M2 Sprint C (June 20 to June 24) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||20-May||Rahul||Tom||M1, Sprint A - met with team; will finalize configuration this week and complete
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:orange"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||20-May||from 1.0||Richard||M1, Sprint C
|- style="background:orange"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||20-May||Meta-data||Saul||M1, Sprint C - at 75% in master, have 10-15% more
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|- style="background:orange"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||20-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:orange"
| User Creation at preinstall - complete||Deliverable completed||1||18-May||RP Notes||Mark (ScottG)||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|- style="background:orange"
| Disk Space Reduction||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|- style="background:orange"
| Share gcc work directories||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:orange"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||20-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style = "background:yellow"
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|- style = "background:yellow"
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D - may be removed
|- style = "background:yellow"
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||20-May||from 1.0||Josh||M1 Sprint D
|- style = "background:yellow"
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||20-May||Meta-data||Saul (Edwin)||M1, Sprint D
|- style = "background:yellow"
| Package reporting system enhancement||||2||20-May||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|- style = "background:yellow"
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||on-going||Meta-data||WR Distro Team||M1, Sprint D
|- style = "background:orange"
| 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||23-May||Meta-data||Mark||M1, Sprint D
|- style = "background:yellow"
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||20-May||RP Notes||Jessica||M1, Sprint D
|-style = "background:yellow"
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||20-May||RP Notes||Saul (Nitin)||M1, Sprint D
|- style = "background:yellow"
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||19-May||Nitin||Nitin||M1, Sprint D
|- style = "background:yellow"
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||20-May||Tom||Tom||M1, Sprint D - development done, needs to be pulled into kernel. Also, testing needs to be done.
|- style = "background:yellow"
| BBXM||Pull in bits from OE (kernel and uboot)||1||20-May||Darren||Darren||M1, Sprint D - uboot for May 20th; kernel may slip to M2
|- style = "background:yellow"
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||20-May||ADT Team||Jessica||M1, Sprint D - need Richard\'s review to finish
|- style = "background:yellow"
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||20-May||Beth||Beth/Scott||M1, Sprint D
|- style = "background:yellow"
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||20-May||from 1.0||Tom||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-18T14:43:39Z

Jnfleisc: /* M2 Sprint A (June 6 to June 10) */ added 17-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||20-May||Rahul||Tom||M1, Sprint A - met with team; will finalize configuration this week and complete
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:orange"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||20-May||from 1.0||Richard||M1, Sprint C
|- style="background:orange"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||20-May||Meta-data||Saul||M1, Sprint C - at 75% in master, have 10-15% more
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|- style="background:orange"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||20-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:orange"
| User Creation at preinstall - complete||Deliverable completed||1||18-May||RP Notes||Mark (ScottG)||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|- style="background:orange"
| Disk Space Reduction||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|- style="background:orange"
| Share gcc work directories||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:orange"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||20-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style = "background:yellow"
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|- style = "background:yellow"
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D - may be removed
|- style = "background:yellow"
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||20-May||from 1.0||Josh||M1 Sprint D
|- style = "background:yellow"
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||20-May||Meta-data||Saul (Edwin)||M1, Sprint D
|- style = "background:yellow"
| Package reporting system enhancement||||2||20-May||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|- style = "background:yellow"
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||on-going||Meta-data||WR Distro Team||M1, Sprint D
|- style = "background:orange"
| 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||23-May||Meta-data||Mark||M1, Sprint D
|- style = "background:yellow"
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||20-May||RP Notes||Jessica||M1, Sprint D
|-style = "background:yellow"
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||20-May||RP Notes||Saul (Nitin)||M1, Sprint D
|- style = "background:yellow"
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||19-May||Nitin||Nitin||M1, Sprint D
|- style = "background:yellow"
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||20-May||Tom||Tom||M1, Sprint D - development done, needs to be pulled into kernel. Also, testing needs to be done.
|- style = "background:yellow"
| BBXM||Pull in bits from OE (kernel and uboot)||1||20-May||Darren||Darren||M1, Sprint D - uboot for May 20th; kernel may slip to M2
|- style = "background:yellow"
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||20-May||ADT Team||Jessica||M1, Sprint D - need Richard\'s review to finish
|- style = "background:yellow"
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||20-May||Beth||Beth/Scott||M1, Sprint D
|- style = "background:yellow"
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||20-May||from 1.0||Tom||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib infrastructure - configuration changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (configuration changes)||1||M2, Sprint A||from 1.0||Richard (Qing)||M2, Sprint A
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Done||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M2, Sprint A||Beth||Beth||M2, Sprint A
|-
| Performance Improvements - split libc||a) Split libc locale generation from libc do_install/do_package||1||Review||Richard||Dongxiao||M2, Sprint A - Dongxiao has a WIP patch. Do we have an ETA on that?
|-
| Performance Improvements - share src dirs||b) Share the source directories for gcc, glibc and maybe others||1||Review||Richard||Richard||M2, Sprint A - RP wrote a proof of concept patch, needs further work, on Yocto schedule for 1.1
|-
| Performance Improvements - CCACHE per recipe||c) Set CCACHE on a per recipe basis. need to figure out whether ccache data can be shared and under what circumstances.||1||Review||Richard||Richard||M2, Sprint A - Idea talked about, no code yet
|-
| Performance Improvements - cache result||d) Cache do_configure autoreconf result||1||Review||Richard||Richard||M2, Sprint A - We know this is about 50% of the time on configure, no code yet. Need fixes to SRC_URI variable dependency code to include checksums (which we need to fix regardless)
|-
| Performance Improvements - remove perl-native from bld dep||e) Remove perl-native from most build dependencies by installing it into its own sysroot||1||Review||Richard||Richard||M2, Sprint A - WIP
|-
| Performance Improvements - documentation||f) Document performance best practises (e.g. no premempt in kernel, use server kernel on ubuntu)||1||Review||Richard||Richard||M2, Sprint A Status: Not done yet.
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Yocto PM||M2, Sprint A - The Yocto Advocacy team is discussing. Yocto PM will monitor to see what engineering work is needed.
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-18T14:42:41Z

Jnfleisc: /* M1 Sprint D (May 16 to May 20) */ added 17-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||20-May||Rahul||Tom||M1, Sprint A - met with team; will finalize configuration this week and complete
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:orange"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||20-May||from 1.0||Richard||M1, Sprint C
|- style="background:orange"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||20-May||Meta-data||Saul||M1, Sprint C - at 75% in master, have 10-15% more
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|- style="background:orange"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||20-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:orange"
| User Creation at preinstall - complete||Deliverable completed||1||18-May||RP Notes||Mark (ScottG)||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|- style="background:orange"
| Disk Space Reduction||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|- style="background:orange"
| Share gcc work directories||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:orange"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||20-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style = "background:yellow"
| multi-lib infrastructure - toolchain changes||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (multilib toolchain changes)||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|- style = "background:yellow"
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D - may be removed
|- style = "background:yellow"
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||20-May||from 1.0||Josh||M1 Sprint D
|- style = "background:yellow"
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||20-May||Meta-data||Saul (Edwin)||M1, Sprint D
|- style = "background:yellow"
| Package reporting system enhancement||||2||20-May||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|- style = "background:yellow"
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||on-going||Meta-data||WR Distro Team||M1, Sprint D
|- style = "background:orange"
| 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||23-May||Meta-data||Mark||M1, Sprint D
|- style = "background:yellow"
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||20-May||RP Notes||Jessica||M1, Sprint D
|-style = "background:yellow"
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||20-May||RP Notes||Saul (Nitin)||M1, Sprint D
|- style = "background:yellow"
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||19-May||Nitin||Nitin||M1, Sprint D
|- style = "background:yellow"
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||20-May||Tom||Tom||M1, Sprint D - development done, needs to be pulled into kernel. Also, testing needs to be done.
|- style = "background:yellow"
| BBXM||Pull in bits from OE (kernel and uboot)||1||20-May||Darren||Darren||M1, Sprint D - uboot for May 20th; kernel may slip to M2
|- style = "background:yellow"
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||20-May||ADT Team||Jessica||M1, Sprint D - need Richard\'s review to finish
|- style = "background:yellow"
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes ~2 weeks)||1||20-May||Beth||Beth||M1, Sprint D
|- style = "background:yellow"
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||20-May||Beth||Beth/Scott||M1, Sprint D
|- style = "background:yellow"
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||20-May||from 1.0||Tom||M1, Sprint D
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-18T14:39:24Z

Jnfleisc: /* M1 Sprint C (May 9 to May 13) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||20-May||Rahul||Tom||M1, Sprint A - met with team; will finalize configuration this week and complete
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:orange"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||20-May||from 1.0||Richard||M1, Sprint C
|- style="background:orange"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||20-May||Meta-data||Saul||M1, Sprint C - at 75% in master, have 10-15% more
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|- style="background:orange"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||20-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:orange"
| User Creation at preinstall - complete||Deliverable completed||1||18-May||RP Notes||Mark (ScottG)||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD.
|- style="background:orange"
| Disk Space Reduction||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|- style="background:orange"
| Share gcc work directories||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:orange"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||20-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-17T19:23:42Z

Jnfleisc: /* M1 Sprint C (May 9 to May 13) */ added 17-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||20-May||Rahul||Tom||M1, Sprint A - met with team; will finalize configuration this week and complete
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||Done||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure - bbclass extend||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend)||1||Done||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:orange"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||20-May||from 1.0||Richard||M1, Sprint C
|- style="background:orange"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||20-May||Meta-data||Saul||M1, Sprint C - at 75% in master, have 10-15% more
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Done||Meta-data||Saul (Dongxiao)|| M1, Sprint C - design done; implementation starting; team in PRC will work on getting machine with 3G modem and SIM card; if there are kernel issues, vendor needs to add this in BSP
|- style="background:orange"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||20-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:orange"
| User Creation at preinstall - complete||Deliverable completed||1||18-May||RP Notes||Mark (ScottG)||M1, Sprint C
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Done||from 1.0||Richard/Dongxiao||M1, Sprint C - Richard sent out summary email summarizing where we are at for performance. 90 minutes is possible. 60 minutes TBD. Julie to look at Richard\'s email and extract tasks.
|- style="background:orange"
| Disk Space Reduction||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|- style="background:orange"
| Share gcc work directories||||2||Update||Team||WR Distro Team||M1, Sprint C - part of Enhanced Performance (Julie to update)
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:orange"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||20-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-17T19:12:36Z

Jnfleisc: /* M1 Sprint A (Apr 25 to Apr 29) */ added 17-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||20-May||Rahul||Tom||M1, Sprint A - met with team; will finalize configuration this week and complete
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style="background:yellow"
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C - patch sent, waiting for checkin
|- style="background:yellow"
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:yellow"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|- style="background:yellow"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|- style="background:yellow"
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|- style="background:yellow"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:yellow"
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|- style="background:yellow"
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|- style="background:yellow"
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|- style="background:yellow"
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:yellow"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto Project v1.0.1 Release Criteria

2011-05-17T16:35:42Z

Jnfleisc: /* Yocto Project 1.0.1 Release Criteria */ added 17-May status

== Yocto Project 1.0.1 Release Criteria ==
Yocto Project 1.0.1 is a point release from Yocto Project 1.0. In general, it contains critical bug fixes as well as nice to have items that are small, well-contained and provide a high benefit to include.

The criteria for adding a code submission into 1.0.1 are that the change:
* Addresses a High priority issue. (Typically, these have critical or major severity.)
* Is small and simple to evaluate (both in lines of code and complexity)
* Fixes a specific problem which users are likely to encounter
* Fixes that problem in a clearly defined way
* Is self contained and unlikely to interact badly with other parts of the system
* Fixes known/clear bugs

Good candidate changes are ones which:
* Address usability issues
* Address host specific issues, particularly in releases of distros that come out after our release
* Address post release bugs users are hitting and reporting
* Address security issues

Bad candidate changes include:
* Significant changes of version (point release for security problems are acceptable)
* Anything involves major code changes where changes cannot be reviewed individually or separated out
* Adding new features
* Changes that break the layout or compatibility with existing builds
* Changes that would trigger significant rebuilds

{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Target''' || ! scope="col" bgcolor="grey" | '''Status'''
|-
| Functional Completion || No new significant features are added. Any minor functionality added is documented in git logs. || bgcolor="#39FF14" | List of commits has been defined and reviewed and all bugs are in the release.
|-
| Build and Release (Yocto) || 1.0.1 build can be built with no errors. || bgcolor="#39FF14" | Build was successful.
|-
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || N/A - BSPs will not be built for 1.0.1.
|-
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="red" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.0%20PointRelease 1 bug] exists for 1.0.1 - not a show-stopper? [http://bugzilla.pokylinux.org/show_bug.cgi?id=1029 bug 1029] exists for 1.0.1 - If this is a regression from 1.0, then it needs to be fixed. We will continue with a full QA test pass and meet on the 19th to discuss status. If this issue is addressed, a full test pass may not need to be needed after fixing. [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.0%20PointRelease 39 bugs total]
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | Full test pass May 13-18. Results posted for go/no-go on 19th. Compliance tests will not be done for 1.0.1. preliminary results available - bug 1029 exists in 1.0.1
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="yellow" | BSPs need to be tested for 1.0.1.
|-
| Documentation || 1.0.1 Release Notes are complete. || bgcolor="yellow" | Release notes will include high priority bugs fixed, pointer to bugzilla, security advisories.
|-
| Build Performance || 1.0.1 does not increase performance above 107 minutes on a developer machine. || bgcolor="yellow" | We have increased build time (~2 minutes) due to a fix, but this was a concsious decision by the team.
|-
| Publication || 1.0.1 release is built and announced to the community. ||
|}

Yocto Project v1.0.1 Release Criteria

2011-05-17T14:26:11Z

Jnfleisc: /* Yocto Project 1.0.1 Release Criteria */ added 17-May status

== Yocto Project 1.0.1 Release Criteria ==
Yocto Project 1.0.1 is a point release from Yocto Project 1.0. In general, it contains critical bug fixes as well as nice to have items that are small, well-contained and provide a high benefit to include.

The criteria for adding a code submission into 1.0.1 are that the change:
* Addresses a High priority issue. (Typically, these have critical or major severity.)
* Is small and simple to evaluate (both in lines of code and complexity)
* Fixes a specific problem which users are likely to encounter
* Fixes that problem in a clearly defined way
* Is self contained and unlikely to interact badly with other parts of the system
* Fixes known/clear bugs

Good candidate changes are ones which:
* Address usability issues
* Address host specific issues, particularly in releases of distros that come out after our release
* Address post release bugs users are hitting and reporting
* Address security issues

Bad candidate changes include:
* Significant changes of version (point release for security problems are acceptable)
* Anything involves major code changes where changes cannot be reviewed individually or separated out
* Adding new features
* Changes that break the layout or compatibility with existing builds
* Changes that would trigger significant rebuilds

{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Target''' || ! scope="col" bgcolor="grey" | '''Status'''
|-
| Functional Completion || No new significant features are added. Any minor functionality added is documented in git logs. || bgcolor="#39FF14" | List of commits has been defined and reviewed and all bugs are in the release.
|-
| Build and Release (Yocto) || 1.0.1 build can be built with no errors. || bgcolor="#39FF14" | Build was successful.
|-
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || N/A - BSPs will not be built for 1.0.1.
|-
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="red" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.0%20PointRelease 1 bug] exists for 1.0.1 - not a show-stopper? [http://bugzilla.pokylinux.org/show_bug.cgi?id=1029 bug 1029] exists for 1.0.1 - show-stopper? [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.0%20PointRelease 39 bugs total]
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | Full test pass May 13-18. Results posted for go/no-go on 19th. Compliance tests will not be done for 1.0.1. preliminary results available - bug 1029 exists in 1.0.1
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || N/A - BSPs will not be built for 1.0.1.
|-
| Documentation || 1.0.1 Release Notes are complete. || bgcolor="yellow" | Release notes to begin May 14th. Need text
|-
| Build Performance || 1.0.1 does not increase performance above 107 minutes on a developer machine. || TBD
|-
| Publication || 1.0.1 release is built and announced to the community. ||
|}

Yocto 1.1 Schedule

2011-05-16T21:55:43Z

Jnfleisc: /* M1 Sprint C (May 9 to May 13) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style="background:yellow"
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C - patch sent, waiting for checkin
|- style="background:yellow"
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:yellow"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|- style="background:yellow"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|- style="background:yellow"
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|- style="background:yellow"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:yellow"
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|- style="background:yellow"
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|- style="background:yellow"
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|- style="background:yellow"
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:yellow"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto Project v1.0.1 Release Criteria

2011-05-16T20:35:53Z

Jnfleisc: /* Yocto Project 1.0.1 Release Criteria */

== Yocto Project 1.0.1 Release Criteria ==
Yocto Project 1.0.1 is a point release from Yocto Project 1.0. In general, it contains critical bug fixes as well as nice to have items that are small, well-contained and provide a high benefit to include.

The criteria for adding a code submission into 1.0.1 are that the change:
* Addresses a High priority issue. (Typically, these have critical or major severity.)
* Is small and simple to evaluate (both in lines of code and complexity)
* Fixes a specific problem which users are likely to encounter
* Fixes that problem in a clearly defined way
* Is self contained and unlikely to interact badly with other parts of the system
* Fixes known/clear bugs

Good candidate changes are ones which:
* Address usability issues
* Address host specific issues, particularly in releases of distros that come out after our release
* Address post release bugs users are hitting and reporting
* Address security issues

Bad candidate changes include:
* Significant changes of version (point release for security problems are acceptable)
* Anything involves major code changes where changes cannot be reviewed individually or separated out
* Adding new features
* Changes that break the layout or compatibility with existing builds
* Changes that would trigger significant rebuilds

{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Target''' || ! scope="col" bgcolor="grey" | '''Status'''
|-
| Functional Completion || No new significant features are added. Any minor functionality added is documented in git logs. || bgcolor="#39FF14" | List of commits has been defined and reviewed and all bugs are in the release.
|-
| Build and Release (Yocto) || 1.0.1 build can be built with no errors. || bgcolor="#39FF14" | Build was successful.
|-
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || N/A - BSPs will not be built for 1.0.1.
|-
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="yellow" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.0%20PointRelease 17 bugs] exist for 1.0.1 so far; triage team will disposition to ensure we have the right list. [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.0%20PointRelease 30 bugs total]
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || Full test pass May 13-18. Results posted for go/no-go on 19th. Compliance tests will not be done for 1.0.1.
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || N/A - BSPs will not be built for 1.0.1.
|-
| Documentation || 1.0.1 Release Notes are complete. || Release notes to begin May 14th.
|-
| Build Performance || 1.0.1 does not increase performance above 107 minutes on a developer machine. ||
|-
| Publication || 1.0.1 release is built and announced to the community. ||
|}

Yocto 1.1 Schedule

2011-05-13T23:24:39Z

Jnfleisc: /* M3 Design (Jul 11 to Jul 15) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style="background:yellow"
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|- style="background:yellow"
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:yellow"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|- style="background:yellow"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|- style="background:yellow"
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|- style="background:yellow"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:yellow"
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|- style="background:yellow"
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|- style="background:yellow"
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|- style="background:yellow"
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:yellow"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week.
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| PAM patch integration - Stage 4||Perform PAM patch integrationDeliverable: A single pull request from Scott (containing SOB\'s by both Robert and Scott) which includes updated recipes/patches for all the recipes on the list created during Stage 1.||2||Accept||Meta-data||Robert||M3, Design
|}

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-13T23:22:59Z

Jnfleisc: /* M2 Stabilize (July 4 to July 15) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style="background:yellow"
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|- style="background:yellow"
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:yellow"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|- style="background:yellow"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|- style="background:yellow"
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|- style="background:yellow"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:yellow"
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|- style="background:yellow"
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|- style="background:yellow"
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|- style="background:yellow"
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:yellow"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| PAM patch integration - Stage 3||Develop a test/verification plan for PAM featuresDeliverable: wiki page describing how to validate that the desired PAM features are working.||2||Accept||Meta-data||Scott||M2, Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-13T23:21:58Z

Jnfleisc: /* M2 Sprint D (June 27 to July 1) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style="background:yellow"
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|- style="background:yellow"
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:yellow"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|- style="background:yellow"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|- style="background:yellow"
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|- style="background:yellow"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:yellow"
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|- style="background:yellow"
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|- style="background:yellow"
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|- style="background:yellow"
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:yellow"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| PAM patch integration - Stage 2||Identify the sources of upstream PAM patches to useDeliverable: A list of our recipes to PAM-enable and the source of patches we intend to use for each recipe. This list must be reviewed and approved by Scott before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-13T23:20:40Z

Jnfleisc: /* M2 Sprint C (June 20 to June 24) */ added 13-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style="background:yellow"
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|- style="background:yellow"
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:yellow"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|- style="background:yellow"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|- style="background:yellow"
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|- style="background:yellow"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:yellow"
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|- style="background:yellow"
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|- style="background:yellow"
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|- style="background:yellow"
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:yellow"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| PAM patch integration - Stage 1||Identify which Yocto recipes will be PAM-enabledDeliverable: A final list of which packages we need to enable PAM for. The list must be reviewed and approved by both Richard and Mark Hatle before it is considered complete.||2||Accept||Meta-data||Robert||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in.||1||M2, Sprint C||Beth||Beth||M2, Sprint C RFC has been reviewed.
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-13T23:15:25Z

Jnfleisc: /* M1 Sprint C (May 9 to May 13) */ added 13-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|- style="background:yellow"
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|- style="background:yellow"
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|- style="background:yellow"
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|- style="background:yellow"
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|- style="background:yellow"
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|- style="background:yellow"
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||Done||RP Notes||Jessica||M1, Sprint C
|- style="background:yellow"
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||Done||Tracey||Scott/Beth||M1, Sprint C
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|- style="background:yellow"
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|- style="background:yellow"
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|- style="background:yellow"
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|- style="background:yellow"
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-13T20:01:02Z

Jnfleisc: /* M1 Sprint A (Apr 25 to Apr 29) */ added 13-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style="background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|-
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||Done||Beth||Beth||M1, Sprint A
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|-
| pam patch integration||add PAM patches throughout the system switchable via the PAM feature (Mark H)||2||Mark checking||Meta-data||WR Distro team||M1, Sprint C - does WR Distro own? Need to get true timeline from them. Mark will follow up.
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||13-May||RP Notes||Jessica||M1, Sprint C
|-
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||13-May||Tracey||Scott/Beth||M1, Sprint C - may be able to include Beth\'s scripts by EOW - Scott done
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|-
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto Project v1.0.1 Release Criteria

2011-05-13T14:59:31Z

Jnfleisc: /* Yocto Project 1.0.1 Release Criteria */

== Yocto Project 1.0.1 Release Criteria ==
Yocto Project 1.0.1 is a point release from Yocto Project 1.0. In general, it contains critical bug fixes as well as nice to have items that are small, well-contained and provide a high benefit to include.

The criteria for adding a code submission into 1.0.1 are that the change:
* Addresses a High priority issue. (Typically, these have critical or major severity.)
* Is small and simple to evaluate (both in lines of code and complexity)
* Fixes a specific problem which users are likely to encounter
* Fixes that problem in a clearly defined way
* Is self contained and unlikely to interact badly with other parts of the system
* Fixes known/clear bugs

Good candidate changes are ones which:
* Address usability issues
* Address host specific issues, particularly in releases of distros that come out after our release
* Address post release bugs users are hitting and reporting
* Address security issues

Bad candidate changes include:
* Significant changes of version (point release for security problems are acceptable)
* Anything involves major code changes where changes cannot be reviewed individually or separated out
* Adding new features
* Changes that break the layout or compatibility with existing builds
* Changes that would trigger significant rebuilds

{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Target''' || ! scope="col" bgcolor="grey" | '''Status'''
|-
| Functional Completion || No new significant features are added. Any minor functionality added is documented in git logs. || bgcolor="#39FF14" | List of commits has been defined and reviewed
|-
| Build and Release (Yocto) || 1.0.1 build can be built with no errors. || bgcolor="yellow" | Build will run May 14th to May 21st. Beth will run a test build the week of May 3rd. She has a plan that doesn't require getting new hardware to do.
|-
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || bgcolor="yellow" | Build will run May 14th to May 21st. Beth will run a test build the week of May 3rd. She has a plan that doesn't require getting new hardware to do.
|-
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="yellow" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.0%20PointRelease 17 bugs] exist for 1.0.1 so far; triage team will disposition to ensure we have the right list. [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.0%20PointRelease 30 bugs total]
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || Full test pass May 13-18. Results posted for go/no-go on 19th.
|-
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || Full test pass May 13-18. Results posted for go/no-go on 19th.
|-
| Documentation || 1.0.1 Release Notes are complete. || Release notes to begin May 14th.
|-
| Build Performance || 1.0.1 does not increase performance above 107 minutes on a developer machine. ||
|-
| Publication || 1.0.1 release is built and announced to the community. ||
|}

Yocto 1.1 Schedule

2011-05-12T14:19:29Z

Jnfleisc: /* M2 Sprint D (June 27 to July 1) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style= "background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|- style= "background: orange"
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in. (takes 2 days)||1||11-May||Beth||Beth||M1, Sprint A RFC is out. Beth/Richard need to talk May 10th.
|- style= "background: orange"
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||12-May||Beth||Beth||M1, Sprint A - did with 1/2 of team; will do with next 1/2 this week
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|-
| pam patch integration||add PAM patches throughout the system switchable via the PAM feature (Mark H)||2||Mark checking||Meta-data||WR Distro team||M1, Sprint C - does WR Distro own? Need to get true timeline from them. Mark will follow up.
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||13-May||RP Notes||Jessica||M1, Sprint C
|-
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||13-May||Tracey||Scott/Beth||M1, Sprint C - may be able to include Beth\'s scripts by EOW - Scott done
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|-
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-12T14:18:52Z

Jnfleisc: /* M2 Sprint B (June 13 to June 17) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style= "background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|- style= "background: orange"
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in. (takes 2 days)||1||11-May||Beth||Beth||M1, Sprint A RFC is out. Beth/Richard need to talk May 10th.
|- style= "background: orange"
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||12-May||Beth||Beth||M1, Sprint A - did with 1/2 of team; will do with next 1/2 this week
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|-
| pam patch integration||add PAM patches throughout the system switchable via the PAM feature (Mark H)||2||Mark checking||Meta-data||WR Distro team||M1, Sprint C - does WR Distro own? Need to get true timeline from them. Mark will follow up.
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||13-May||RP Notes||Jessica||M1, Sprint C
|-
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||13-May||Tracey||Scott/Beth||M1, Sprint C - may be able to include Beth\'s scripts by EOW - Scott done
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|-
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-12T00:46:09Z

Jnfleisc: /* M4 (Aug 15 to Oct 6 -- Stabilize Complete Aug 29, Release Complete Oct 3) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style= "background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|- style= "background: orange"
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in. (takes 2 days)||1||11-May||Beth||Beth||M1, Sprint A RFC is out. Beth/Richard need to talk May 10th.
|- style= "background: orange"
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||12-May||Beth||Beth||M1, Sprint A - did with 1/2 of team; will do with next 1/2 this week
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|-
| pam patch integration||add PAM patches throughout the system switchable via the PAM feature (Mark H)||2||Mark checking||Meta-data||WR Distro team||M1, Sprint C - does WR Distro own? Need to get true timeline from them. Mark will follow up.
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||13-May||RP Notes||Jessica||M1, Sprint C
|-
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||13-May||Tracey||Scott/Beth||M1, Sprint C - may be able to include Beth\'s scripts by EOW - Scott done
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|-
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time). Note: This document will include documentation on how to use multiple versions of a library (with clutter as the example library).
||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-11T14:54:13Z

Jnfleisc: /* M1 Sprint C (May 9 to May 13) */

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style= "background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|- style= "background: orange"
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in. (takes 2 days)||1||11-May||Beth||Beth||M1, Sprint A RFC is out. Beth/Richard need to talk May 10th.
|- style= "background: orange"
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||12-May||Beth||Beth||M1, Sprint A - did with 1/2 of team; will do with next 1/2 this week
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||13-May||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|-
| pam patch integration||add PAM patches throughout the system switchable via the PAM feature (Mark H)||2||Mark checking||Meta-data||WR Distro team||M1, Sprint C - does WR Distro own? Need to get true timeline from them. Mark will follow up.
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||13-May||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||13-May||RP Notes||Jessica||M1, Sprint C
|-
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||13-May||Tracey||Scott/Beth||M1, Sprint C - may be able to include Beth\'s scripts by EOW - Scott done
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|-
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time).||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-10T21:17:52Z

Jnfleisc: /* M2 Sprint B (June 13 to June 17) */ added package doc audit 50%

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style= "background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|- style= "background: orange"
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in. (takes 2 days)||1||11-May||Beth||Beth||M1, Sprint A RFC is out. Beth/Richard need to talk May 10th.
|- style= "background: orange"
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||12-May||Beth||Beth||M1, Sprint A - did with 1/2 of team; will do with next 1/2 this week
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Saul checking||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|-
| pam patch integration||add PAM patches throughout the system switchable via the PAM feature (Mark H)||2||Mark checking||Meta-data||WR Distro team||M1, Sprint C - does WR Distro own? Need to get true timeline from them. Mark will follow up.
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Saul checking||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||13-May||RP Notes||Jessica||M1, Sprint C
|-
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||13-May||Tracey||Scott/Beth||M1, Sprint C - may be able to include Beth\'s scripts by EOW - Scott done
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|-
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| Package Documentation Audit: 50% of recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. This is a status check to ensure we have made progress on 1/2 of them.||2||Accept||Team||Scott G||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}

=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time).||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}

Yocto 1.1 Schedule

2011-05-10T19:58:09Z

Jnfleisc: /* M3 Sprint A (Jul 18 to Jul 22) */ added 10-May status

= Yocto Project 1.1 (release date: October 6, 2011) =
----
The detailed milestone map for the 1.1 release of Yocto Project is as below.
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]

== 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

'''pre-M1 COMPLETED'''

== M1 (Apr 18 to Jun 13 -- Design Complete Apr 25, Dev Complete May 23, Stabilize Complete Jun 6, Release Complete Jun 13) ==
=== M1 Design (Apr 18 to Apr 22) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Automatically generate package repos - design||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations; also, documentation of this process is essential; this stage is the design phase.||2||Done||Team||Saul (Dexuan)||M1, Design
|-
| OE Autobuilder rename||||1||Done||Beth||Beth||M1, Design
|-
| Strip out LSB, non-LSB build work||Remove the LSB, non-LSB build work done at the end of 1.0 and re-incorporate it with sstate||1||Done||Beth||Beth||M1, Design - one minor problem
|}

=== M1 Sprint A (Apr 25 to Apr 29) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| OE-Core||Restructuring, renaming, rebranding||1||Done||RP Notes||Richard||M1, Sprint A - only remaining piece is for OE Core to work without setting a distro (wasn\'t originally scheduled) - this is a new task for EO this week
|-
| SDK support in sanity test framework||This task includes enabling unfs and toolchain testing in sanity test framework, enabling toolchain testing on PRC autobuilder||1||Done||QA||Jiajun/Meilei||M1, Sprint A
|-
| User Creation at preinstall - status check||Design status check||1||Done||RP Notes||Mark (ScottG)||M1, Sprint A architecture was sent out as RFC
|-
| Check SRCREV in recipe files||should work, may need dev||2||Done||RP Notes||Richard/Ke||M1, Sprint A
|-
| Refactor BSPs to use topic branches|| crownbay and fish river island BSP need to be changed to make use of the new eg20t/emgd/gma500 topic branches ||2||Done||Tom||Tom||M1, Sprint A When other branches (ex. FRI 2) are added, they will use topic branches.
|- style= "background: orange"
| Additional config options||The following configurations need to be enabled to support DPDK: glibc > 2.7 (for features related to cpuset), kernel configuration: HPET and HPET MMAP configuration options enabled, all UIO kernel options enabled, HUGETLBFS enabled, PROC_PAGE_MONITOR enabled||1||13-May||Rahul||Tom||M1, Sprint A Waiting on ECG
|- style= "background: orange"
| Autobuilder maintenance||Bring scripts into configuration or get git repo working for those that can\'t be brought in. (takes 2 days)||1||11-May||Beth||Beth||M1, Sprint A RFC is out. Beth/Richard need to talk May 10th.
|- style= "background: orange"
| Retrospective||Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team.||1||12-May||Beth||Beth||M1, Sprint A - did with 1/2 of team; will do with next 1/2 this week
|}

=== M1 Sprint B (May 2 to May 6) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Design||Design/Architect the Layer Tooling approach||1||Done||Architect||Richard||M1 Sprint B Paul and PRC discussed this morning, and Paul has had some discussion with Richard. Don\'t have 100% of schedule.
|-
| Test Plan||Create an overall Test Plan for 1.1 and post on Wiki||1||Done||Jiajun||Jiajun||M1, Sprint B
|-
| Sync qemugl with MeeGo - Status check||This is a status check on how the work to sync qemugl with MeeGo is going. Completion set for M1, Sprint D.||2||Done||Meta-data||Saul (Edwin)||M1, Sprint B - on track.
|-
| Finish LSB \"distribution\" work - QT3||QT3 work is complete.||2||Done||Meta-data||WR Distro Team||M1, Sprint B - patch is pending, need to figure out landing location
|-
| Incompatible License||Design and Review milestone||2||Done||Paul||Paul||M1, Sprint B - See RFC at http://www.mail-archive.com/yocto@yoctoproject.org/msg01078.html
|-
| Changes for Image Creator - phase 1||Phase 1: add mechanism to enable selection of server backend at runtime||1||Done||ADT Team||Jessica||M1, Sprint B
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Done||from 1.0||Scott G||M1, Sprint B - Scott is running the world build and we will examine the data to determine next steps.
|-
| Fast boot analysis||Perform analysis to determine how best to implement a 2 second boot time||1||Done||Darren||Darren||M1, Sprint B - Darren has provided kernel data - http://dvhart.com/darren/yocto/boottime/. Still needs to do user space.
|-
| Build Yocto behind firewall - plan||Josh/Darren define plan||2||Done||Dave||Darren, Joshua||M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Josh put his plan and code beginnings in bugzilla.
|}

=== M1 Sprint C (May 9 to May 13) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| crazygit fetcher||TI issues with fetch2 - per LCS - should this be a P1?||2||13-May||RP Notes||Saul (Ke)||M1, Sprint C
|-
| multi-lib infrastructure||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time - infrastructure in place (bbclass extend and multilib toolchain changes)||1||13-May||from 1.0||Richard (Qing)||M1, Sprint C
|-
| Package config option enhancement - Plan||Plan our approach to package config option enhancement||2||13-May||from 1.0||Richard||M1, Sprint C
|-
| Upstream our patches - phase 1||Have upstream status updated on 90% of patches (so that we can have a status update)||1||Accept||Meta-data||Saul||M1, Sprint C - we won\'t be at 90% - Saul will have numbers by EOW and we can revise estimate.
|-
| 3G - Design||We have an ofono recipe but need some integration work done. This milestone is a status check and design update. HW needs to be received at this time.||2||Saul checking||Meta-data||Saul (Dongxiao)|| M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
|-
| pam patch integration||add PAM patches throughout the system switchable via the PAM feature (Mark H)||2||Mark checking||Meta-data||WR Distro team||M1, Sprint C - does WR Distro own? Need to get true timeline from them. Mark will follow up.
|-
| Automatically generate package repos - complete||automatically generate package repositories (and be able to \"use them\" -- to be defined) for both ipk and rpm/zypper combinations as discussed during the Design phase; also, documentation of this process is essential||2||Saul checking||Team||Saul (Dexuan)||M1, Sprint C
|-
| network based PR service||A network based service to repot PR value based on poky task checksum||2||13-May||RP Notes||Jessica||M1, Sprint C
|-
| User Creation at preinstall - complete||Deliverable completed||1||13-May||RP Notes||Mark (ScottG)||M1, Sprint C - may have a slight slip
|-
| BSP image creation||Add text on the website that tells users how to create images from the BSP source. Note: This may include a script to enable the creation.||1||13-May||Tracey||Scott/Beth||M1, Sprint C - may be able to include Beth\'s scripts by EOW - Scott done
|-
| Tarball Doc process||Right now tarball docs are frozen shortly before a release. The tarball never gets updated beyond that during subsequent documentation development. However, website docs are periodically updated as changes are made during the next development cycle. We need a documentation process where the tarball docs are updated along with the website docs. Perhaps releasing and building a separate documentation tarball is an answer... This whole scheme needs thought about and something implemented.||1||Done||From scratch||ScottR||M1, Sprint C - Just waiting for yocto-docs repo to be merged.
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance - long-term goal is to build in under 1 hour; short-term goal is to build faster than v1.0This is a task to define the performance plan.||1||Accept||from 1.0||Richard/Dongxiao||M1, Sprint C
|-
| Disk Space Reduction||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| Share gcc work directories||||2||Saul checking||Team||WR Distro Team||M1, Sprint C - WR distro team has put out RFCs and waiting for comments - we need timeline
|-
| kernel port to 2.6.37||Port the kernel to 2.6.37||1||Done||Darren||Darren||M1, Sprint C - complete, pending pull from Saul
|-
| Tracing: Add Systemtap support for userspace tracing||Add utrace, etc||2||13-May||Tom||Tom||M1, Sprint C
|}

=== M1 Sprint D (May 16 to May 20) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib recipe update||recipes for multi-lib updated||1||M1, Sprint D||from 1.0||Richard (Qing)||M1, Sprint D
|-
| multi-lib RPM||RPM support for multilib added||1||Accept||from 1.0||Richard (Qing)||M1, Sprint D
|-
| Image Creator - 1.0 finish|| finish the Image Creator to add features pushed out from 1.0 - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details||1||Accept||from 1.0||Josh||M1 Sprint D
|-
| Sync qemugl with MeeGo - COMPLETE||sync qemugl with MeeGo is complete||2||Accept||Meta-data||Saul (Edwin)||M1, Sprint D
|-
| Package reporting system enhancement||||2||M1, Sprint D||Meta-data||Saul (Lei)||M1, Sprint D (need additional definition of this item)
|-
| Finish LSB \"distribution\" work - ID failures||Identify issues in order to: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M1, Sprint D
|-
| 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||Meta-data||Mark||M1, Sprint D
|-
| End of package revision||Use the network based PR service to get the PR values which will go into package feed.||2||Accept||RP Notes||Jessica||M1, Sprint D
|-
| x32 - plan||layer to support toolchain, libc, and kernel - Plan created||2||Accept||RP Notes||Saul (Nitin)||M1, Sprint D
|-
| Upgrade to gcc 4.6||Need to upgrade toolchain to gcc 4.6||1||M1, Sprint D||Nitin||Nitin||M1, Sprint D - Nitin has been supplying gcc 4.6 patches. Request out to team to switch to gcc 4.6. There was a report on a mailing list that ARM USB doesn\'t work with gcc 4.6, which needs to be addressed.
|-
| Optimize support for Intel hardware features||We need to understand and track each important Intel hardware feature and how it should be optimally supported in the Intel BSPS. Items that immediately come to mind are power, video, and performance counter settings, etc.||1||on-going||Tom||Tom/Darren||M1, Sprint D - Tom is working on perf support.
|-
| Upgrade EMGD||EMGD needs to be upgraded to the latest version (1.6), which may require MESA 7.10.2. A big part of this should also be to make sure everything gets tested and works e.g. 3-d games, video acceleration, etc||2||M1, Sprint D||Tom||Tom||M1, Sprint D - Currently investigating X driver unresolved variable problems. Tom will keep Beth in the loop because there are autobuilder implications.
|-
| BBXM||Pull in bits from OE (kernel and uboot)||1||Accept||Darren||Darren||M1, Sprint D
|-
| Eclipse-native tools interface||More integrated with upstream once there\'s integrated Linux tools that meets our need, e.g. lttng-remote||2||Accept||ADT Team||Jessica||M1, Sprint D
|-
| Changes for Image Creator - phase 2||Phase 2: Bug fix for 7.70||1||Accept||ADT Team||Jessica||M1, Sprint D
|-
| License tracking||Get common licenses for all packages and consolidate base file licenses. (takes ~3 days)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| 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||M1, Sprint D
|-
| Release Scripts||Create Release Scripts that can be used for both a weekly release and for Yocto 1.1 release to be run by autobuilder (a week. testing on this may take longer)||1||M1, Sprint D||Beth||Beth||M1, Sprint D
|-
| Fix Documentation Publishing||fix our documentation publishing so that documents can be published at any time||1||Accept||Beth||Beth/Scott||M1, Sprint D
|-
| Tracing: perf trace scripting support||Basically this means allowing perf to be built with the Perl and Python bindings, which turned out to be a headache last time.||2||Accept||from 1.0||Tom||M1, Sprint D
|-
| Demo||Need to determine what we will do for demo and find an owner||1||M1, Sprint D||Team||Julie||M1, Sprint D - Julie to kick off discussions and find an owner
|}

=== M1 Stabilize (May 23 to June 3) ===
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Development complete||All bugs targeted for 1.0.1 are in the 1.0.1 build.||1||Accept||Team||All||M1, Sprint3 to M1, Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M1 Release (June 6 to June 13) ===

Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M2 Design (May 30 to June 3) ===
* Working week. No tasks complete this week.

=== M2 Sprint A (June 6 to June 10) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Finish LSB \"distribution\" work - complete||Complete all work: Merge patches which are pushed during yocto 1.0. Add packages(qt3,xdg-* ...) LSB Test Suite need. Hardware platform x86 and ppc32(if qt4 can be supported) can be finished.||2||Accept||Meta-data||WR Distro Team||M2, Sprint A
|-
| Live images||make live images their own image type||2||Accept||RP Notes||Saul||M2, Sprint A
|-
| Optimise Configure||||2||Plan defined||RP Notes||Saul (Dongxiao)||M2, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Audotbuilder infrastructure||Bring up additional autobuilders and work with sysadmin to configure.||1||M2, Sprint A||Beth||Beth||M2, Sprint A (depends on having sysadmin support)
|}

=== M2 Sprint B (June 13 to June 17) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Layer Tooling - Architecture||Implement Layer Tooling changes||1||Accept||Architect||Richard (Paul/Daoxien will help)||M2 Sprint B
|-
| Error handling in bitbake||desc||1||Accept||RP Notes||Saul (Scott G)||M2, Sprint B
|-
| Package config option enhancement - Implement||Implement approach defined in plan for package config option enhancement||2||Accept||from 1.0||Saul||M2, Sprint B
|-
| Upstream our patches - phase 2||Everyone has attempted upstreams for patches defined from phase 1||1||Accept||Meta-data||Saul||M2, Sprint B
|-
| MeeGo GPLv2 Sync||compare with Yocto, sync any patches||2||Accept||RP Notes||Saul (Ke)||M2, Sprint B
|-
| Directory Ownership||||1.5||Accept||RP Notes||Mark (w/Qing)||M2, Sprint B
|-
| Changes for Image Creator - phase 3||Phase 3: package format job done + image output type job done||1||Accept||ADT Team||Jessica||M2, Sprint B
|-
| 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||M2, Sprint B
|-
| kernel bloat - analysis||target = boot a minimal image in < 8M - analysis complete||1||Accept||Darren||Darren||M2, Sprint B
|}
=== M2 Sprint C (June 20 to June 24) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| multi-lib complete||multi-lib support for 32-bit & 64-bit and capable of being installed at the same time fully complete||1||Accept||from 1.0||Richard (Qing)||M2, Sprint C - exact date TBD
|-
| Monitor disk availability||Monitor disk availability and warn the user if it is running low. May only focus on a few directories, for example: poky/build and poky/build/downloads, this would solve the multiple mount point problem||2||Review||RP and Robert||WR Distro Team||M2, Sprint C
|-
| btrfs||||2||Accept||Meta-data||Saul (Nitin)||M2, Sprint C
|-
| adding eglibc config control||this goes with the package config options||1.5||Accept||RP Notes||Mark||M2, Sprint C
|-
| Implement Continuous Autobuilds||Build constantly instead of daily (need fuzz builds for this. once fuzz builds are implemented, this is trivial)||2||Accept||from 1.0||Beth||M2, Sprint C
|}

=== M2 Sprint D (June 27 to July 1) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Image Creator polish||polish and refine Image Creator - See https://wiki.yoctoproject.org/wiki/BitBake/GUI/PostOneOh for details ||1||Accept||from 1.0||Josh||M2, Sprint D
|-
| Clean up warning messages||A build that runs correctly to completion still includes a ton of WARNING messages. We need a project to clean these up. Beth will work on License Warnings, team will look at other logfile warnings||2||Accept||davest and RP||Saul||M2, Sprint D
|-
| 3G - Complete||We have an ofono recipe but need some integration work done - This milestone checks that 3G is complete.||2||Accept||Meta-data||Saul (Dongxiao)||M2, Sprint D
|-
| running post installs at rootfs gen time||||2||Accept||RP Notes||Saul (Dexuan)||M2, Sprint D
|-
| remove gnome-vfs||||3||Accept||RP Notes||Saul (Edwin)||M2, Sprint D
|-
| x32 - complete||layer to support toolchain, libc, and kernel - x32 is complete||2||Accept||RP Notes||Saul (Nitin)||M2, Sprint D
|-
| BSP update/intro||determine and integrate / create arch reference BSPs (e500, Cortex, ARM, MIPs)||2||Accept||Bruce/Richard/team||Bruce||M2, Sprint D
|-
| Changes for Image Creator - phase 4||Phase 4: complete plug-in||1||Accept||ADT Team||Jessica||M2, Sprint D
|-
| Enhance the deploy part in remote debug||ADT is currently using org.eclipse.cdt.remote.launch for remote debug. One limitation in this plug-in is that it can only deploy one single file to the target during the debug. Though it is ok for debugging static linked program, debugging dynamic linked program might require deploying multiple files(including executables and libraries) to the target.||2||Accept||Lianhao||Jessica||M2 Sprint D
|-
| BSP builds||Autobuilder git fetcher improvements (3 days)||2||Accept||from 1.0||Beth||M2, Sprint D
|-
| kernel bloat - development||target = boot a minimal image in < 8M - development complete||1||Accept||Darren||Darren||M2, Sprint D
|-
| Tracing: Systemtap usability in Yocto||Right now, there are instructions on the wiki on how to configure and use Systemtap with Yocto. While straightforward, they are tedious and unlikely to be useful to most people pressed for time. We need to make it easier to use - in addition to documentation/HOWTO tasks listed elsewhere on this page, we need to make it usable \'out of the box\' (i.e. outside of ADT) e.g. all paths and configuration handled via script or something similar||2||Accept||Tom||Tom||M2, Sprint D
|-
| Tracing/profiling HOWTOs||Create a document or extend the current Yocto tracing wiki page to explain in detail how to use all the tracing tools in Yocto. It should detail not only how to use each tool individually, but also how to use them in conjunction with each other, highlighting situations in which each is most useful. There should also be some extensive worked examples of real-life use-cases and how they could be investigated using the Yocto tracing/profiling tools.||2||Accept||Tom||Tom||M2, Sprint D
|}

=== M2 Stabilize (July 4 to July 15) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|-
| Lock kernel version||lock the kernel version||1||Accept||Team||Darren||M2, Stabilize (ww29)
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M2 Release (July 18 to July 22) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

=== M3 Design (Jul 11 to Jul 15) ===
* Working week. No tasks complete this week.

=== M3 Sprint A (Jul 18 to Jul 22) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Publish Shared State||Publish the shared state information.||2||Review||LCS||Beth||M3, Sprint A if Richard confirms some answers to questions
|-
| Upstream our patches - phase 3||Another round of updates is complete||1||Accept||Meta-data||Saul||M3, Sprint A
|-
| Sanity checks on per recipe basis||||2||Accept||RP Notes Bug#405||Saul (Scott G)||M3, Sprint A
|-
| Ability to build SRPM||||3||Accept||RP Notes||Jeff Polk/Mark||M3, Sprint A - Julie to check with Jeff
|-
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Moved from M1||Meta-data||WR Distro team||M3, Sprint A
|-
| Fish River Island/Fish River Island II BSP(s)||The base Fish River Island BSP exists already, we now need to add support for the extra devices, and add support for changes introduced by Fish River Island II||2||Accept||Tom||Tom||M3, Sprint A
|-
| More test cases about toolchain in autobuilder||||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Indigo update||Update to the latest Eclipse release (Indigo)||2||Accept||ADT Team||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Systemtap integration||Make it easy and convenient for the user to write and execute Systemtap scripts from the IDE. http://www.eclipse.org/linuxtools/projectPages/systemtap/ might provide a good starting point and may be something we can contribute to. We may also need to contribute further up the chain to provide e.g. remote target capabilities.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| \'perf scripting\' integration||Make it easy and convenient for the user to write and execute \'perf scripts\' from the IDE. We should be able to leverage and build on the Systemtap integration for this.||2||Accept||Tom||Jessica||Status check in M2, Sprint A, M3, Sprint A
|-
| Package Documentation Audit: All recipes build||31 recipes were identified as not building during the package documentation audit done in M1, Sprint B. Those all need to build and we need to re-run a new package documentation audit.||2||Accept||Team||Scott G||M3, Sprint A

|-
| Update Quick Start for 1.1||Ensure Quick Start guide has latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Update Reference Manual for 1.1||Ensure Reference Manual has the latest 1.1 information, including details on how to use Image Creator.||2||Accept||Dave||ScottR||M3, Sprint A
|-
| Additions to build stats||||1||Accept||Beth||Beth||M3, Sprint A
|-
| build statistics reporting||As someone interested in how long it takes to build different images on different hardware configurations and other assorted build metrics, I would like a web based service, that takes output generated by an extended buildstats.bbclass and stores it, to compare against different machines. The end result should be a way to visualize the collected data. See: https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions||||M3, Sprint A||eflanagan/Jay7/ka6sox||Beth/Jay||M3, Sprint A - discussions posted on Wiki
|-
| Fast boot time||2 second boot time target||1||Accept||Team||Darren||M3, Sprint A - analysis will be complete to show where slowdown is coming from (BIOS or elsewhere); the earliest we can get a system that can use BLDK is August 1st, so getting to the 2s target in 1.1 is not likely
|-
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||M3, Sprint A
|-
| Alpha||Begin an alpha program after the stabilization period for M3.||1||Accept||Team||Julie||M3, Sprint A
|}

=== M3 Stabilize (Jul 25 to Aug 5) ===
{| border = "1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Be prepared for Distro upgrades||Our release is right around the time of the 6monthly distro release dates, we should accommodate for this in our testing plan||2||Accept||Joshua||Jiajun||check latest distribution in M1 Stabilize, M2 Stabilize, and M3 Stabilize and test them in milestone testing; Should we include more Distributions, besides fedora, ubuntu and opensuse?
|-
| Test Execution Plan||Create a Test Execution Plan for the milestone and send to developers||1||Accept||Jiajun||Jiajun||M1 Stabilize; M2 Stabilize; M3 Stabilize
|}

==== Stabilize schedule ====
'''Week 1'''
* Day 1, 2: Weekly test pass
* Day 3: Pre-Release Readiness meeting
* If there are issues:
** Day 4, 5: Fix issues and repeat Week 1
* If there are not issues:
** Day 4, 5 and beginning of Week 2: Complete a full test pass

'''Week 2'''
* Day 1, 2, 3: Complete full test pass
* Day 4: Release Readiness meeting
* If there are issues, fix and repeat from Week 1
* If there are not issues, proceed to Release phase

=== M3 Release (Aug 8 to Aug 15) ===
Follow Release Checklist, which includes:
* Release is packaged
* Release is pushed to mirrors
* Release is announced to community via mailing lists and blog

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

{|border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| 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 overviews the major development pieces such as recipe creation, building, debugging, publishing, fail-safing, back-door hook creation, etc. This manual will also include migration information. Scoping would be about two weeks and length would probably be about 40 pages. Overall development time will likely take up to the release given my experience on the creation of the ADT manual (there is no uniterruped time).||1||Not Started||from scratch||ScottR||M4, Scott will send the more detailed milestones
|-
| Various Demo Videos||The idea here is to create screen-capture type tutorials similar to what exists for the ADT Eclipse Plug-in. However, we want to contract out some help for professional voice-over talent to be used with the images. These don\'t have to be limited to screen-capture material but could include well-done PPT decks - similar to how other business units in Intel create various training modules. For 1.1 it would be good to capture the script for the existing ADT Eclipse Plug-in module and have it voiced over. Also, for 1.1 it would be good to create a similar module for the Image Creator application.||2||Not Started||From ADT module and scratch||ScottR||Q3 at the earliest
|-
| Open-source Newbie Information||This information will be for developers new to open-source. These people do not know what IRC means. Targeted for developers coming from a non-open-source environment. I think the best place for this information would be the website. I haven\'t looked yet but I suspect information already exists on the web. For Yocto it will be a matter of collecting the best and most useful information, orginizing it and properly referencing/leveraging it.||2||Not Started||From scratch||ScottR||M4, this is part of the Yocto Development Guide
|-
| OOB documentation||Create an out of box guide for giveaway systems built using Yocto.||1||Accept||Julie||ScottR||Julie to research timing on this. ~Q3 is current thinking.
|}

{|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 ||
|}

== Not Scheduled List ==
{| border="1"
| align="center" style="background:#f0f0f0;"|'''Feature Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Priority'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Owner'''
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
|-
| Web-based Image Creator||Create a web-based interface that does what the Image Creator does.||2.5||Review||LCS||Jason Kridner?||not scheduled at this time - depends on Image Creator completing
|-
| Recipe-specific sysroot||||3||Review||from 1.0||Saul (Dongxiao)||not scheduled at this time (1 month task)
|-
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|-
| Executable images||Create images that are executable - for example a pre-installed Ubuntu image with YP installed||3||Review||LCS||||Not scheduled at this time
|-
| Self-hosting image||Create customizable chroot; Build an image that would be self-hosting||2.5||Review||LCS||||Not scheduled at this time
|-
| Yocto OOPS-type messages||add the equivalent of kernel OOPS to Yocto||2.5||Review||LCS||||Not scheduled at this time
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||Review||LCS||||Not scheduled at this time
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||not scheduled at this time
|-
| Test framework||this is a test framework that we can include in the distribution||3||Review||RP Notes||||not scheduled at this time - Is it the TI’s test framework we discussed before? A: Not necessarily, we\'re still waiting for someone to step up and really take ownership of this area but it needs some resource commitment as its not a simple task.
|-
| Replacement for video/audio players currently in Yocto||Codec…||3||Review||Meta-data||||Not scheduled at this time
|-
| Investigate New UI||For demos, we would like need a reference UI that is not Sato. Investigate possibilities that the Yocto team won\'t need to maintain. OpenBox? Gnome-desktop? GP? LXDE? KDE Mobile?||3||Review||Meta-data||||Not scheduled at this time
|-
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not scheduled at this time - we just need to document how to use multiple versions of a library using clutter as the example
|-
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||Not scheduled at this time
|-
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|-
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|-
| Prebuit SDK integration||speedup target image generation by reusing prebuilt tools from SDK native and target binaries. See: http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration||2||Reject||Adrian||Jessica||not scheduled at this time - This functionality looks to have been provided by sstate packages?
|-
| Patch Test System||Create a machine where developers can upload/test patches before submitting them to master to ensure builds won\'t break when patches are added. (developer autobuilders? Fuzz builds?)||2||Review||Team||Jiajun||not scheduled at this time - although, team is investigating other mechanisms for ensuring that patches submitted don\'t break build
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
|-
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|-
| Bugzilla to Wiki||Create a script which automatically populates and updates the Wiki based on changes in bugzilla.||2.5||Review||Darren||||not scheduled at this time
|}