Yocto Project v1.1 Release Criteria: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 24: Line 24:
| Build Performance || Improving build performance. || bgcolor="#39FF14" | Some degradation due to many features integrated. Risk understood, has plan for improvement in M3
| Build Performance || Improving build performance. || bgcolor="#39FF14" | 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) || bgcolor="#39FF14" | Status updated, on track for the release.
| Upstream Commits || Have upstream status updated on 90% of patches (so that we can have a status update) || bgcolor="#39FF14" | Status updated, target met.
|-
|-
| Marketing Deliverables || None || bgcolor="#39FF14" |
| Marketing Deliverables || None || bgcolor="#39FF14" |

Revision as of 17:42, 25 July 2011

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

Yocto Project 1.1

Milestone 2

Release Criteria Milestone 2 Target Milestone 2 Status
Functional Completion All M2 features and BSPs are in the build. Schedule-status-M2.png

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.pokylinux.org/wiki/Yocto_Bug_Trend.
Functional Tests 100% of planned tests are executed and results are logged in bugzilla. Target met. https://wiki.pokylinux.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.pokylinux.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

Milestone 1

Release Criteria Milestone 1 Target Milestone 1 Status
Functional Completion All M1 features and BSPs are in the build. Schedule-status.PNG
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.pokylinux.org/wiki/Yocto_Bug_Trend.
Functional Tests 100% of planned tests are executed and results are logged in bugzilla. https://wiki.pokylinux.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.pokylinux.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