Yocto 1.1 Features

Potential Yocto 1.1 Features

Yocto 1.1 - Target release = October 2011

This page contains a list of Yocto 1.1 features. In early March, the Yocto Architect will issue an official call for Yocto 1.1 features. This list contains reprioritized items from 1.0 or features that came up as a result of discussions among Yocto engineers. If you have a feature you would like to see added, send an email to the Yocto Architect with a description of the feature, its impat on the source code, and whether you are willing to help write the code to implement the feature. The Yocto Architect will add this to the potential Yocto 1.1 Features list. The potential Yocto 1.1 Features list will be turned into the Yocto Features List as described in the Program Management Plan.

Yocto 1.1 Themes

The topics below are the themes that some members of the team have started brainstorming for Yocto 1.1. These will grow and change with community input.

Yocto 1.1 Objectives

The objectives of the Yocto 1.1 release are to grow participation in Yocto and increase the number of BSPs written for Yocto and partner products based on Yocto.

Yocto 1.1 Theme List

The Yocto 1.1 Themes towards the Objectives listed above are:

• Multilibs & OE-core config - This work, which began in Yocto 1.0, needs to be completed.
• Improve ease of BSP creation - Document the lifecycle and process. Possibly create walkthroughs or tutorials to integrate a new board into the linux-yocto kernel.
• Build performance – Get to the goal of 1 hour build time on a developer machine.
• Upstreaming – Submit patches to upstream projects in order to reduce the 2,000+ patches which are currently part of Yocto Project.

Process for Entering New Feature Requests

• Create a new entry in the appropriate feature table below (Poky, SDK, Hardware)
  • Suggestion: start by copying an existing request as a template
• Give the feature a short, descriptive name
• Provide a one or two sentence brief description of the feature
• Set the priority as appropriate (see the legend below)
• Set the Status to "Review"
• In the Source field, enter your name along with the origination of the request (e.g. OSV, OEM, Community) if applicable; provide as much detail here as you can
• In the Comments / Bugzilla field, provide any additional information for the request, such as a link to a bugzilla entry
• Preview your Entry to make sure it looks ok and then save it

Legend

Priority: 1 = Must Have, 2 = Nice to Have, 3 = Optional

Status: Accept = Engineering agreement to include in release, Review = Under Review for Inclusion in this release, Reject = Will not be included in this release

Sample Table

This is a sample table to show how to submit features.

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
Placeholder feature name	Placeholder description of the feature	1, 2, or 3	Review	name	Comment

Architecture

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
Layer Tooling	This includes the architectural work plus implementing the changes.	1	Review	Architect	M2; Owner = Richard
OE-Core	Restructuring, renaming, rebranding	1	Review	RP Notes	M1; Owner = Richard

Poky/Bitbake

This section contains features for the Poky/Bitbake infastructure.

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
Error handling in bitbake	desc	1	Review	RP Notes	M2; Owner = Saul
crazygit fetcher	TI issues with fetch2	2	Review	RP Notes
multi-lib	multi-lib support for 32-bit & 64-bit and capable of being installed at the same time	1	Review	from 1.0	M1; Owner = Richard
Image Creator	finish the Image Creator to add features pushed out from 1.0	1	Review	from 1.0	M2; Owner = Josh + someone else (Dave investigating someone on Jessica's team)
Recipe-specific sysroot		3	Review	from 1.0
Handle old versions in WORKDIR		3	Review	from 1.0
Package config option enhancement	need to plan and then implement	2	Review	from 1.0

QA Items

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
QA Framework Enhancements	Add test for unfs_qemu bootup in the sanity test framework and give Liping his patch (Jiajun) Help to define long-term flexible framework for SDK/meta-toolchain testing.. Under the test folder, we have different groups of test, such as sanity, SDK(tools), meta-toolchain. User could freely select which test cases they want to test. (Control granularity/level group? Or even a single case has a switch) (Jiajun) More test-projects into existing manual test part for meta-toolchain. We should help to find the two typical projects, one c and o C++. (Jiajun) Transform the meta-toolchain manual testing into the unified test-framework. (Liping) Prepare a workable environment for testing all those newly added features. (Liping) After sanity test framework is in the upstream, collect data when selecting different kinds of test components. (MeiLei)	??	Review	QA
Open Source Test Cases	Perform technical, legal, and QA steps necessary to move test cases into open source.	3	Review	QA
Automated test infrastructure	Automate the test infrastructure	2	Review	QA
Test framework	this is a test framework that we can include in the distribution	3	Review	RP Notes
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	Review	Joshua

Meta-data

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
Upstream our patches	We'll add this as a task in a milestone to give people time to do	1	Review	Meta-data	M2; Owner = Saul
3G	We have an ofono recipe but need some integration work doing	2	Review	Meta-data
btrfs		2	Review	Meta-data
Other components?	Saul will investigate other components.	2	Review	Meta-data
Replacement for video/audio players currently in Yocto	Codec…	3	Review	Meta-data
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
Qemugl upstreaming	Opengl ES Support	3	Review	Meta-data
Sync qemugl with MeeGo		2	Review	Meta-data
Package reporting system enhancement		2	Review	Meta-data
pam patch integration	add PAM patches throughout the system switchable via the PAM feature (Mark H)	2	Review	Meta-data
selinux patch integration	add SE Linux patches in a similar way to PAM	3	Review	Meta-data
Finish LSB "distribution" work	Merge patches which are pushed during ycoto 1.0. Add packages LSB Test Suite need. Hardware platform x86, x86-64 and ppc32(if qt4 can be supported) can be finished.	2	Review	Meta-data	M2; Owner = Xiaofeng Yan, Jingdong Lu, Kai kang,Xudong Hao
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	Review	Meta-data	M1; Owner = Mark
Framework to support multiple library versions co-existing	similar to recipe specific sysroot; needs documentation	2	Review	Team
Embedded java environment or even JDK support		3	Review	Team
Automatically generate package repos	automatically generate package repositories (and be able to "use them" -- to be defined) for both ipk and rpm/zypper combinations; NEEDS MORE DISCUSSION	2	Review	Team
MeeGo GPLv2 Sync	compare with Yocto, sync any patches	2	Review	RP Notes
Incompatible License		2	Review	Paul
End of package revision	replace with a network service	2	Review	RP Notes	Owner = Jessica
Target module build	Allow for building kernel modules on the target device	2	Review	RP Notes	Owner = Darren
Live images	make live images their own image type	2	Review	RP Notes	Owner = Saul
multiple update-alternatives	fixed?	3	Review	RP Notes
init scripts	provide an image/recipe skeleton as a canonical example	3	Review	RP Notes
running post installs at rootfs gen time		2	Review	RP Notes
remove gnome-vfs		3	Review	RP Notes
gtk+ sato filechooser patch		3	Review	RP Notes
sato refresh		3	Review	RP Notes
adding eglibc config control	this goes with the package config options	1.5	Review	RP Notes	M2; Owner = Mark
Sanity checks on per recipe basis		2	Review	RP Notes
x32	layer to support toolchain, libc, and kernel	2	Review	RP Notes
User Creation at postinstall		1	Review	RP Notes	M1; Owner = Mark
Directory Ownership		1.5	Review	RP Notes	M2; Owner = Mark
Optimise Configure		2	Review	RP Notes	Performance idea
Ability to build SRPM		3	Review	RP Notes
Check SRCREV in recipe files	should work, may need dev	2	Review	RP Notes
Add Directfb（license LGPL） function	Directfb is more appropriate embedded device than other graphic software	3	Review	Meta-data	M3;Owner = Xiaofeng Yan if possible

BSPs

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
Support for AVX as in kernel 2.6.30. - Already in 1.0	Any toolchain support needed?	1	Review	Jay	M1; Owner = Saul

ADT

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
More test cases about toolchain in autobuilder		2	Review	ADT Team	Owner = Jessica
Eclipse-native tools interface	not using oprofile-UI. More integrated with upstream	2	Review	ADT Team
Indigo update	Update to the latest Eclipse release (Indigo)	2	Review	ADT Team	M2; Owner = Jessica
Changes for Image Creator	Eclipse changes pending Image Creator	1	Review	ADT Team	M2; Owner = Jessica
Secure logging		2	Review	ADT Team
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	Review	Adrian

Documentation

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
Package Documentation Audit	Make changes defined in the package documentation audit from Yocto 1.0	2	Review	from 1.0	Owner = Saul
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	Owner = ScottR
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	Owner = ScottR
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	Owner = ScottR
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.	3	Not Started	From scratch	Owner = ScottR

Build

This section contains requirements related to the build (autobuilder activities, performance, footprint, etc.)

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
Autobuilder maintenance	Bring scripts into configuration or get git repo working for those that can't be brought in.	1	Review	Beth	M1; Owner = Beth
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	Review	Beth	M2; Owner = Beth
License tracking	Get common licenses for all packages. (takes ~3 days)	1	Review	Beth	M1; Owner = Beth
License history	Build a parser to do license history more gracefully and make sure all recipes are correct. (takes ~2 weeks)	1	Review	Beth	M2; Owner = Beth
Audotbuilder infrastructure	Bring up additional autobuilders and work with sysadmin to configure.	1	Review	Beth	M2; Owner = Beth
Overall Project	Host a retrospective to discuss what went well and what can be improved in Yocto 1.0.	1	Review	Beth	M1; Owner = Beth
Release Scripts	Create Release Scripts for OCT 2011 release.	1	Review	Beth	M3; Owner = Beth
Enhanced Performance	Also, environmental requirements/suggestions for expected performance; Goal is to build in under 1 hour	2	Review	from 1.0
Disk Space Reduction		2	Review	Team
Share gcc work directories		2	Review	Team
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.	2	Review	Team
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		Review	eflanagan/Jay7/ka6sox
BSP builds	Autobuilder git fetcher improvements	2	Review	from 1.0	M1; Owner = Beth
Implement Continuous Autobuilds	Build constantly instead of daily	2	Review	from 1.0	M1; Owner = Beth

Performance and Usability

This section contains general Yocto performance as well as usability items.

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
Fast boot time	2 second boot time target	1	Review	Team	M2; Owner = Darren
Build Yocto behind firewall	Darren will investigate site.conf and documentation	2	Review	Dave
Minimal Image unique	make minimal image smaller	3	Review	Team
POSIX support	address POSIX failures found in 1.1	2	Review	Team

Kernel

This section contains items specific to the Yocto kernel.

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
BSP kernel config audit	audit kernel configs for the various BSPS	2	Review	Team
Tracing: perf trace scripting support	we think usability is the direction to focus on, we want to improve usability through documentation	2	Review	from 1.0
Tracing: tuna, oscilloscope recipes	catch up with Tom, likely to remove	3	Review	from 1.0

Project-Wide Features

This section contains features for the entire project or for the project website or mailing lists.

Feature Name	Description	Priority	Status	Source	Comments / Bugzilla Links
Patchwork	is it worth the overhead, are there alternatives	3	Review	RP Notes
Alpha	Begin an alpha program after the stabilization period for M3.	1	Review	Team
Bugzilla to Wiki	Create a script which automatically populates and updates the Wiki based on changes in bugzilla.	?	Review	Darren