Yocto Project v1.1 Release Criteria

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

Yocto Project 1.1

Milestone 4

Release Criteria	Milestone 4 Target	Milestone 4 Status
Functional Completion	A significant part of all the 1.1 Med+ bug fixes and BSPs are in the build.	see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for details Remaining Med+ bugs: 1.1 remaining bugs (Med+) Fixed 186 bugs as of 10/17/2011
Build and Release (Yocto)	All M4 bug fixes can be built with no errors.	RC4 generated, full test complete, no show stoppers or major issues.
Build and Release (BSPs)	Core and meta-intel BSPs can be built with no errors.	All BSPs build with no problem
Open Bugs	All bugs have been dispositioned. High issues have been fixed.	[1] - 0 new bugs for 1.1. HIGH priority bugs - 0 high bugs for 1.1 See trend chart at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Functional Tests	100% of planned tests are executed and results are logged in bugzilla.	Complete https://wiki.yoctoproject.org/wiki/Yocto_1.1_Milestone_Test_Report
Distros Tested	Fedora, Ubuntu, Opensuse (N+1)	Fedora 15, Ubuntu 11.04, Opensuse 11.4, Fedora 16 Alpha, Ubuntu 11.10 Alpha3, Opensuse 12.1 M5: Complete and all passed
BSP Testing	100% of planned tests are executed and results are logged in bugzilla.	Complete https://wiki.yoctoproject.org/wiki/Yocto_1.1_Milestone_Test_Report
Documentation	All documents listed in M4 feature list	Doc pull request sent, complete
Build Performance	None	N/A
Upstream Commits	Have upstream status updated on 90% of patches (so that we can have a status update)	Complete
Marketing Deliverables	None	N/A
Publication	Yocto 1.1 release is announced

Milestone 3

Release Criteria	Milestone 3 Target	Milestone 3 Status
Functional Completion	All M3 features and BSPs are in the build.	see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for details
Build and Release (Yocto)	All M3 features can be built with no errors.	RC3 generated, build is good with minor issues
Build and Release (BSPs)	Core and meta-intel BSPs can be built with no errors.	RC3 generated, build is good with minor issues
Open Bugs	All bugs have been dispositioned. High issues have been fixed.	NEW bugs - 0 new bugs for M3. HIGH priority bugs - 1 high bugs for M3, already fixed See trend chart at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Functional Tests	100% of planned tests are executed and results are logged in bugzilla.	There are known problems, but we have fix in master. Bug trend is going to the right direction. WDD is down. https://wiki.yoctoproject.org/wiki/Yocto_1.1_Milestone_Test_Report
Distros Tested	Fedora, Ubuntu, Opensuse	Fedora15 build failed, but fixed in master, Opensuse 11.4 and Ubuntu 11.04 pass.
BSP Testing	100% of planned tests are executed and results are logged in bugzilla.	We are good here. https://wiki.yoctoproject.org/wiki/Yocto_1.1_Milestone_Test_Report
Documentation	None
Build Performance	RFC ready	RFC sent
Upstream Commits	Have upstream status updated on 90% of patches (so that we can have a status update)	Target met
Marketing Deliverables	None
Publication	M3 release is announced	Complete

Milestone 2

Release Criteria	Milestone 2 Target	Milestone 2 Status
Functional Completion	All M2 features and BSPs are in the build.	see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for details
Build and Release (Yocto)	All M2 features can be built with no errors.	M2 RC3 generated, pulled in as many features as possible
Build and Release (BSPs)	Core and meta-intel BSPs can be built with no errors.	Target met
Open Bugs	All bugs have been dispositioned. High issues have been fixed.	NEW bugs - No new bugs for M2. HIGH priority bugs - no high bugs for M2 See trend chart at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Functional Tests	100% of planned tests are executed and results are logged in bugzilla.	Target met. https://wiki.yoctoproject.org/wiki/Yocto_1.1_Milestone_Test_Report
Distros Tested	Fedora, Ubuntu, Opensuse	Fedora15, Opensuse 11.4 and Ubuntu 11.04.
BSP Testing	100% of planned tests are executed and results are logged in bugzilla.	Target met. https://wiki.yoctoproject.org/wiki/Yocto_1.1_Milestone_Test_Report
Documentation	A reviewable draft of the Yocto Project Development Guide.	On Track
Build Performance	Improving build performance.	Some degradation due to many features integrated. Risk understood, has plan for improvement in M3
Upstream Commits	Have upstream status updated on 90% of patches (so that we can have a status update)	Status updated, target met.
Marketing Deliverables	None
Publication	M2 release is announced	Announced to the public via yoctoproject.org mailing list

Milestone 1

Release Criteria	Milestone 1 Target	Milestone 1 Status
Functional Completion	All M1 features and BSPs are in the build.	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.	Build pulled in all fixes possible.
Build and Release (BSPs)	Core and meta-intel BSPs can be built with no errors.	Build pulled in all fixes possible.
Open Bugs	All bugs have been dispositioned. High issues have been fixed.	NEW bugs - 1 unaccepted New bugs for 1.1 M1. HIGH priority bugs - no HIGH priority bugs for 1.1 M1 See trend chart at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.
Functional Tests	100% of planned tests are executed and results are logged in bugzilla.	https://wiki.yoctoproject.org/wiki/Yocto_1.1_Milestone_Test_Report
Distros Tested	Fedora, Ubuntu, Opensuse	Fedora 14, Ubuntu 11.04, Opensuse 11.4
BSP Testing	100% of planned tests are executed and results are logged in bugzilla.	https://wiki.yoctoproject.org/wiki/Yocto_1.1_Milestone_Test_Report
Documentation	M1 documentation deliverables are complete.	Only deliverable is allowing documentation to be updated even after code freeze. On-track.
Build Performance	Plan for improving performance is defined.	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)	At 85%, which is good enough for alpha.
Marketing Deliverables	Giveaway plans defined	At least one giveaway plan has been defined and is in the process of being implemented.
Publication	M1 release is announced	Complete