Yocto Project v1.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

Release Criteria	Target	Status
Functional Completion	No new significant features are added. Any minor functionality added is documented in git logs.	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.	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.	Open bug query shows one bug - not a show-stopper? New bugs found during testing: bug 1029 exists for 1.0.1 - Is this a regression from 1.0? bug 1087 was just found Total bug count: 39 bugs total
Functional Tests	100% of planned tests are executed and results are logged in bugzilla.	Compliance tests will not be done for 1.0.1.
BSP Testing	100% of planned tests are executed and results are logged in bugzilla.	WEEKLY TESTING ONLY was done. See above for high level status. Two bugs: bug 1029: Beagleboard cannot boot up from uboot bug 1087: libzypp fails to do_compile for crownbay
Documentation	1.0.1 Release Notes are complete.	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.	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.