Yocto Project v1.0 Release Criteria: Difference between revisions
From Yocto Project
Jump to navigationJump to search
Line 26: | Line 26: | ||
| All bugs dispositioned; Show-stoppers fixed | | All bugs dispositioned; Show-stoppers fixed | ||
''Current criteria: All bugs have been dispositioned.'' | ''Current criteria: All bugs have been dispositioned.'' | ||
| bgcolor="orange" | | | bgcolor="orange" | 23 bugs have not been dispositioned (still in "New" state); Owners: Tom, Saul, Richard, Julie, Paul, Mark, Ke, Jeff, Edwin | ||
|- | |- | ||
! scope="row" | Functional Tests | ! scope="row" | Functional Tests |
Revision as of 00:24, 15 February 2011
Yocto v1.0 Release Criteria
Release Criteria | Target | Status |
---|---|---|
Functional Completion | All M1, M2, M3 functional features implemented by EO M3
Current Criteria: Functional features are ready to go into master. |
see Yocto 1.0 Schedule#Stabilization Phase Features and Activities |
Build and Release
(Yocto) |
Yocto 1.0 code builds reliably
Current criteria: All features in master can be built. |
on-track to have stable builds by the end of Master Stabilization phase |
Build and Release
(BSPs) |
Yocto BSPs build reliably
Current criteria: Plan in place to build/QA BSPs by EO Feb. |
Meeting Thursday to determine plan. Next Wednesday, the BSP build server will be off-line for a move, which may impact dates. |
Open Bugs | All bugs dispositioned; Show-stoppers fixed
Current criteria: All bugs have been dispositioned. |
23 bugs have not been dispositioned (still in "New" state); Owners: Tom, Saul, Richard, Julie, Paul, Mark, Ke, Jeff, Edwin |
Functional Tests | 100% of planned tests executed and all bugs are logged in bugzilla
Current criteria: Weekly testing is performed on master and all bugs in bugzilla |
testing starts in Feb |
BSP Testing | 100% of planned BSP tests executed
Current criteria: TBD - pending BSP plan |
|
Alpha Feedback | Alpha feedback included
Current criteria: Alpha begins Feb 11th |
on-track; need to ensure autobuilder caches the sources (it does) and need to ensure someone can perform a build using autobuilder as the pre-mirror; also need a tag on the build for alpha; Julie will work with Saul and Beth on this. |
Documentation | Release documentation created and published
Current criteria: M4 schedule items completed |
on-track |
Build Performance | Build takes 90 minutes (stretch goal = one hour) to do a complete rebuild of local sources of poky-image-sato on a developer's desktop. (The one we are using is: Intel(R) Core(TM) i7 CPU 940 @ 2.93GHz, 8 siblings, 4 cpu cores, total mem 6118644k, with: MACHINE=qemux86, BB_NUMBER_THREADS = "8", PARALLEL_MAKE = "-j 6", and only rpm packaging.)
Current criteria: Team has begun tracking these metrics per build and has defined plan to do engineering work to address. |
investigating who can do this rebuild testing regularly |
Marketing requirements complete | Engineering requirements to the marketing plan are complete
Current criteria: Engineering requirements to the marketing plan are known. |
need details on requirements |
Publication | Release and documentation are published on yoctoproject.org
Current criteria: None for this stage |
Tunnel Creek BSP Release Criteria
Release Criteria | Target | Status |
---|---|---|
Development progress | Features implemented; Code completed | Coding completed |
Build and Release | EMGD and non-EMGD BSPs build reliably | Still building image with removable media fix. |
Open Bugs | All bugs dispositioned; Show-stoppers fixed | TBD based on testing of latest build |
Functional Tests | 100% of planned tests executed | Tom and Jaijun will test when final build is available. |
Legal Compliance | All legal requirements met | Plan in place to create click-through. Getting host set up. |
Documentation | Release Notes created and published | |
Performance | Performance targets achieved | This will be done out of cycle. |
Publication | Release and documentation are published on yoctoproject.org | on-track |
Laverne Point Release Criteria
Release Criteria | Target | Status |
---|---|---|
Development Progress | Coding complete | Coding completed |
Build and Release | Code builds reliably | Release candidate is built. |
Open Bugs | All bugs dispositioned; Show-stoppers fixed | No opens are show-stoppers. Open issues will be ID'd in release notes. |
Functional Tests | 100% of planned tests executed | testing completed |
Legal Compliance | All legal requirements met | tools run; requirements met |
Performance | Performance targets achieved | N/A |
Publication | Release and documentation are published on yoctoproject.org | Complete |