Yocto 1.1 Schedule: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(→‎Not Scheduled List: added 4-May status)
Line 498: Line 498:
| align="center" style="background:#f0f0f0;"|'''Comments / Bugzilla Links'''
| 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?||Depends on Image Creator completing, so stretch goal.
| 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)||will not schedule for 1.1 (will take 1 month)
| 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
| Handle old versions in WORKDIR||||3||Review||from 1.0||||Not scheduled at this time
|- style="background: yellow"
| 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||Saul will get the Sprint information from WR.
|-
|-
| 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
| 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
Line 513: Line 511:
|-
|-
| Reduced depth revision history||Decrease the depth of the revision history||3||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
|- style="background: yellow"
| Ability to archive work dir||Add the ability to archive the work directory to handle the GPL compliance issue.||3||Review||LCS||||Not scheduled at this time - could go into janitor list
|-
|-
| Open Source Test Cases||Perform technical, legal, and QA steps necessary to move test cases into open source.||3||Review||QA||||may have no resource to do this task
| 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||||\"may have no resource to do this task;Is it the TIfs 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. \"
| 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.  
|- style="background: yellow"
| Other components?||Saul will investigate other components.||2||Review||Meta-data||Saul||
|-
|-
| Replacement for video/audio players currently in Yocto||Codecc||3||Review||Meta-data||||Not scheduled at this time
| 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
| 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
| Qemugl upstreaming||Opengl ES Support||3||Review||Meta-data||||Not scheduled at this time
|- style="background: yellow"
| pam patch integration||add PAM patches throughout the system switchable via the PAM feature (Mark H)||2||Review||Meta-data||WR Distro Team ?||
|-
|-
| selinux patch integration||add SE Linux patches in a similar way to PAM||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"
|- style="background: yellow"
| Framework to support multiple library versions co-existing||similar to recipe specific sysroot; needs documentation||3||Review||Team||Saul (Dongxiao?)||Not for 1.1; we just need to document how to use multiple versions of a library using clutter as the example
| 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
| Embedded java environment or even JDK support||||3||Review||Team||||Not scheduled at this time
|- style="background: yellow"
| Target module build||Allow for building kernel modules on the target device||2||Review||RP Notes||Darren||Darren will put this onto the Janitor\'s list
|-
|-
| gtk+ sato filechooser patch||||3||Review||RP Notes||||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
| sato refresh||||3||Review||RP Notes||||Not scheduled at this time
|- style="background: yellow"
| Add Directfbilicense LGPLj function||Directfb is more appropriate embedded device than other graphic software||3||Reject||Meta-data||||Saul will ask Robert why he thinks directfb is already complete
|- style="background: yellow"
| Support ECG (ongoing)||ECG is ramping up with Yocto BSPs and likely will require significant amounts of time and help. Also, since we\'re trading their BSP work for our help in upstreaming patches, we\'re also likely to have to spend a significant amount of time with upstream-related tasks too.||1||Accept||Tom||Tom||Tom will create an on-going task list
|-
|-
| Secure login||||2||Review||ADT Team||Jessica||Mx - may not make it into 1.1
| Secure login||||2||Review||ADT Team||Jessica||not scheduled at this time
|- style="background: yellow"
|-
| Package Documentation Audit||Make changes defined in the package documentation audit from Yocto 1.0||2||Accept||from 1.0||Scott G||M1, Julie ask Scott re: Sprint
| 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?
|- style="background: yellow"
|-
| Enhanced Performance||Also, environmental requirements/suggestions for expected performance; Goal is to build in under 1 hour||1||Review||from 1.0||||
| 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
|- style="background: yellow"
| Disk Space Reduction||||2||Review||Team||WR Distro Team ?||Owner = TBD - WR distro team might be willing to own if they know what is required
|- style="background: yellow"
| Share gcc work directories||||2||Review||Team||WR Distro Team ?||Owner = TBD - WR distro team might be willing to own if they know what is required
|- style="background: yellow"
| 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 ?||
|- style="background: yellow"
| Build Yocto behind firewall - complete||Darren will investigate site.conf and documentation||2||Review||Dave||Darren, Joshua||
|- style="background: yellow"
| POSIX support||address POSIX failures found in 1.1||2||Review||Team||||
|-
|-
| Tracing: tuna, oscilloscope recipes||catch up with Tom, likely to remove||3||Review||from 1.0||||not scheduled at this time
| 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
| Patchwork||is it worth the overhead, are there alternatives||3||Review||RP Notes||||not scheduled at this time
|- style="background: yellow"
| Demo||Need to determine what we will do for demo and find an owner||1||Accept||Team||Julie||Julie to work with team on details and find correct owner.
|-
|-
| 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
| 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
|}
|}

Revision as of 15:25, 5 May 2011

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)

Feature Name Description Priority Status Source Owner 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)

Feature Name Description Priority Status Source Owner 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 5-May QA Jiajun/Meilei M1, Sprint A - My patch has not be pulled in. I will resent patch to Saul for comments. Lei and I have enabled toolchain testing on PRC autobuilder and it could work now. Patch in review.
User Creation at preinstall - status check Design status check 1 Done RP Notes Mark (ScottG) M1, Sprint A architecture was sent out as RFC
Optimise Configure 2 M2, Sprint A RP Notes Saul (Dongxiao) M1, Sprint A - Dongxiao sent a report last week. Question about proving performance on auto-reconf (needs Richard\'s reply). Put final date as M2, Sprint A.
Check SRCREV in recipe files should work, may need dev 2 5-May RP Notes Richard/Ke M1, Sprint A - Ke is in final testing phases of patch.
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 5-May Tom Tom M1, Sprint A Tom is testing with 2.6.39.
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 5-May Rahul Tom M1, Sprint A Tom is testing with 2.6.39.
Autobuilder maintenance Bring scripts into configuration or get git repo working for those that can\'t be brought in. (takes 2 days) 1 6-May Beth Beth M1, Sprint A RFC is out. If accepted, this will be done by May 6th.
Retrospective Hold a retrospective to discuss what went well and what can be improved in 1.1 with the meta-data team. 1 6-May Beth Beth M1, Sprint A

M1 Sprint B (May 2 to May 6)

Feature Name Description Priority Status Source Owner Comments / Bugzilla Links
Layer Tooling - Design Design/Architect the Layer Tooling approach 1 6-May Architect Richard M1 Sprint B Need to ensure Dexuan and Paul are on-board.
crazygit fetcher TI issues with fetch2 - per LCS - should this be a P1? 2 M1, Sprint C RP Notes Saul (Ke) M1, Sprint B (timescale = 2-3 days) Ke needs to push to 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 M1, Sprint C from 1.0 Richard (Qing) M1, Sprint B - Needs to push to M1, Sprint C due to 1.0.1 bugs.
Test Plan Create an overall Test Plan for 1.1 and post on Wiki 1 6-May Jiajun Jiajun M1, Sprint B I am working on the Test Plan and it will be sent out for review this week.
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 3-May Meta-data WR Distro Team M1, Sprint B - patch is pending, need to figure out landing location
Incompatible License Design and Review milestone 2 6-May Paul Paul M1, Sprint B - Paul will send an email next day or so.
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 B, Sprint C, Sprint D - Tom is working on video.
Upgrade EMGD EMGD needs to be upgraded to the latest version (1.6). 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 C Tom Tom M1, Sprint B and Sprint C - Tom got the kernel to the point of fixing this. Some binaries call talloc(), so we may not be able to use. May need 1.6 gold version, which has no talloc(). Then, you need to upgrade to latest MESA (7.10.2). Tom will keep Beth in the loop because there are autobuilder implications.
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
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 M1, Sprint C eflanagan/Jay7/ka6sox Beth/Jay M1, Sprint B and Sprint C (or two weeks in here) - discussions posted on Wiki
Fast boot analysis Perform analysis to determine how best to implement a 2 second boot time 1 9-May Darren Darren M1, Sprint B - Darren has some initial data that he\'s shared with a few people. Lots of opportunity for improvement. Will have more detailed report next call.
Build Yocto behind firewall - plan Josh/Darren define plan 2 9-May Dave Darren, Joshua M1, Sprint B - Josh put some comments and linked to git tree with a sanity check in bug 933. Needs Dave/Richard feedback. Next week set final date for completion.

M1 Sprint C (May 9 to May 13)

Feature Name Description Priority Status Source Owner Comments / Bugzilla Links
multi-lib recipe update recipes for multi-lib updated 1 Accept from 1.0 Richard (Qing) M1, Sprint C - exact date TBD
Package config option enhancement - Plan Plan our approach to package config option enhancement 2 Accept 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
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 Accept Meta-data Saul (Dongxiao) M1, Sprint C Need hardware and infrastructure to test 3G (MeeGo team has this)
Package reporting system enhancement 2 Accept Meta-data Saul (Lei) M1, Sprint C or D (need additional definition of this item)
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 Accept Team Saul (Dexuan) M1, Sprint C
User Creation at preinstall - complete Deliverable completed 1 Accept RP Notes Mark (ScottG) M1, Sprint C
Upgrade to gcc 4.6 Need to upgrade toolchain to gcc 4.6 1 Accept Nitin Nitin M1, Sprint C or D
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 B, Sprint C, Sprint D - Tom is working on video.
Upgrade EMGD EMGD needs to be upgraded to the latest version (1.6). 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 C Tom Tom M1, Sprint B and Sprint C - Tom got the kernel to the point of fixing this. Some binaries call talloc(), so we may not be able to use. May need 1.6 gold version, which has no talloc(). Then, you need to upgrade to latest MESA (7.10.2). Tom will keep Beth in the loop because there are autobuilder implications.
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 Accept 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 Accept From scratch ScottR M1, Sprint C - Scott will work with Richard on this
License tracking Get common licenses for all packages and consolidate base file licenses. (takes ~3 days) 1 Accept Beth Beth M1, Sprint C
Audotbuilder infrastructure Bring up additional autobuilders and work with sysadmin to configure. 1 Accept Beth Beth M1, Sprint C (dependent on us having a system admin)
Release Scripts Create Release Scripts that can be used for both a weekly release and for OCT 2011 release to be run by autobuilder (a week. testing on this may take longer) 1 Accept Beth Beth M1, Sprint C
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 Review from 1.0 Richard/Dongxiao M1, Sprint C
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 M1, Sprint C eflanagan/Jay7/ka6sox Beth/Jay M1, Sprint B and Sprint C (or two weeks in here) - discussions posted on Wiki
kernel port to 2.6.37 Port the kernel to 2.6.37 1 Accept Darren Darren M1, Sprint C
Tracing: Add Systemtap support for userspace tracing Add utrace, etc 2 Accept Tom Tom 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 Accept From scratch ScottR M1, Sprint C - Scott will work with Richard on this

M1 Sprint D (May 16 to May 20)

Feature Name Description Priority Status Source Owner Comments / Bugzilla Links
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
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 replace with a network service 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
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 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
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

M1 Stabilize (May 23 to June 3)

Feature Name Description Priority Status Source Owner 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)

Feature Name Description Priority Status Source Owner Comments / Bugzilla Links
Live images make live images their own image type 2 Accept RP Notes Saul 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
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

M2 Sprint B (June 13 to June 17)

Feature Name Description Priority Status Source Owner 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)

Feature Name Description Priority Status Source Owner 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)

Feature Name Description Priority Status Source Owner 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)

Feature Name Description Priority Status Source Owner 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)

Feature Name Description Priority Status Source Owner Comments / Bugzilla Links
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
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
Additions to build stats 1 Accept Beth Beth M3, Sprint A
Alpha Begin an alpha program after the stabilization period for M3. 1 Accept Team Julie M3, Sprint A
Publish Shared State Publish the shared state information. 2 Review LCS Beth M3, Sprint A if Richard confirms some answers to questions
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
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

M3 Stabilize (Jul 25 to Aug 5)

Feature Name Description Priority Status Source Owner 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)

Feature Name Description Priority Status Source Owner 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.
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

Feature Name Description Priority Status Source Owner 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
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
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_1.1_Schedule&oldid=1614"