Yocto Project v1.1 Release Criteria: Difference between revisions
From Yocto Project
Jump to navigationJump to search
(→Yocto Project 1.1: added 24-May status) |
|||
Line 5: | Line 5: | ||
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status''' | | ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status''' | ||
|- | |- | ||
| Functional Completion || All M1 features and BSPs are in the build. || bgcolor=" | | Functional Completion || All M1 features and BSPs are in the build. || bgcolor="#39FF14" | [[File:Schedule-status.PNG]]<br>All desired features are in build. One documentation publishing fix remains.<br>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. || bgcolor=" | | Build and Release (Yocto) || All M1 features can be built with no errors. || bgcolor="orange" | QEMU build, but full build did not complete. QA is starting a partial test pass on what built. | ||
|- Working | |- Working | ||
| Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="orange" | | | Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="orange" | Crown Bay EMGD had some issues. | ||
|- | |- | ||
| Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor=" | | Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor="yellow" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW NEW bugs] - 3 unaccepted New bugs for 1.1 M1<br>[http://bugzilla.yoctoproject.org/buglist.cgi?priority=High&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=---&target_milestone=0.9%20M1&target_milestone=0.9%20M2&target_milestone=0.9%20M3&target_milestone=0.9%20M4&target_milestone=0.9.1&target_milestone=0.9.2&target_milestone=1.0%20M1&target_milestone=1.0%20M2&target_milestone=1.0%20M3&target_milestone=1.0%20M4&target_milestone=1.1&target_milestone=1.1%20M1&target_milestone=1.1%20M2&target_milestone=1.1%20M3&target_milestone=1.1%20M4&target_milestone=Q1&target_milestone=Q2&target_milestone=Q3&target_milestone=Q4 HIGH priority bugs] - no HIGH priority bugs for 1.1 M1<br>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. || bgcolor="orange" | | | Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | QA can only do weekly test pass. Will begin full test pass when build completes. | ||
|- | |- | ||
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | | | BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="orange" | QA can only do weekly test pass. Will begin full test pass when build completes. | ||
|- | |- | ||
| Documentation || M1 documentation deliverables are complete. || bgcolor="#39FF14" | Only deliverable is allowing documentation to be updated even after code freeze. On-track. | | Documentation || M1 documentation deliverables are complete. || bgcolor="#39FF14" | Only deliverable is allowing documentation to be updated even after code freeze. On-track. | ||
|- | |- | ||
| Build Performance || Plan for improving performance is defined. || bgcolor=" | | Build Performance || Plan for improving performance is defined. || bgcolor="#39FF14" | Performance goals for M1 (mostly planning goals) were met. See schedule for details. | ||
|- | |- | ||
| Upstream Commits || Have upstream status updated on 90% of patches (so that we can have a status update) || bgcolor=" | | Upstream Commits || Have upstream status updated on 90% of patches (so that we can have a status update) || bgcolor="#39FF14" | At 85%, which is good enough for alpha. | ||
|- | |- | ||
| Marketing Deliverables || Giveaway plans defined || bgcolor=" | | Marketing Deliverables || Giveaway plans defined || bgcolor="#39FF14" | At least one giveaway plan has been defined and is in the process of being implemented. | ||
|- | |- | ||
| Publication || M1 release is announced || | | Publication || M1 release is announced || | ||
|} | |} |
Revision as of 14:31, 25 May 2011
The Release Criteria for the various Yocto Project 1.1 releases are below.
Yocto Project 1.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. | QEMU build, but full build did not complete. QA is starting a partial test pass on what built. |
Build and Release (BSPs) | Core and meta-intel BSPs can be built with no errors. | Crown Bay EMGD had some issues. |
Open Bugs | All bugs have been dispositioned. High issues have been fixed. | NEW bugs - 3 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. | QA can only do weekly test pass. Will begin full test pass when build completes. |
BSP Testing | 100% of planned tests are executed and results are logged in bugzilla. | QA can only do weekly test pass. Will begin full test pass when build completes. |
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. |
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 |