Yocto 1.1 Features: Difference between revisions
From Yocto Project
Jump to navigationJump to search
| Line 11: | Line 11: | ||
* Package config option enhancement | * Package config option enhancement | ||
* Build BSPs as part of the nightly builds | * Build BSPs as part of the nightly builds | ||
=== QA Items === | |||
* 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) | |||
Revision as of 02:07, 17 February 2011
Yocto 1.1 Features
This page contains a list of Yocto 1.1 features. There has been no official call for Yocto 1.1 features, so this list is not complete. At this time, this page simply contains Yocto 1.0 features that have been re-prioritized to Yocto 1.1.
- multi-lib (May come in 1.0.1.)
- Full-featured Yocto Image Creator
- Recipe-specific sysroot
- Tracing: perf trace scripting support
- Tracing: tuna, oscilloscope recipes
- Handle old versions in WORKDIR
- Package config option enhancement
- Build BSPs as part of the nightly builds
QA Items
- 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)
