Yocto Project v1.0 Release Criteria: Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
|||
| Line 15: | Line 15: | ||
| Yocto 1.0 code builds reliably | | Yocto 1.0 code builds reliably | ||
''Current criteria: All features in master can be built.'' | ''Current criteria: All features in master can be built.'' | ||
| bgcolor=" | | bgcolor="yellow" | on-track to have stable builds by the end of Master Stabilization phase | ||
|- | |- | ||
! scope="row" | Build and Release | ! scope="row" | Build and Release | ||
| Line 21: | Line 21: | ||
| Yocto BSPs build reliably | | Yocto BSPs build reliably | ||
''Current criteria: Plan in place to build/QA BSPs by EO Feb.'' | ''Current criteria: Plan in place to build/QA BSPs by EO Feb.'' | ||
| bgcolor="yellow" | | | bgcolor="yellow" | Meeting Thursday to determine plan. Next Wednesday, the BSP build server will be off-line for a move, which may impact dates. | ||
|- | |- | ||
! scope="row" | Open Bugs | ! scope="row" | Open Bugs | ||
| Line 41: | Line 41: | ||
| Alpha feedback included | | Alpha feedback included | ||
''Current criteria: Alpha begins Feb 11th'' | ''Current criteria: Alpha begins Feb 11th'' | ||
| bgcolor="yellow" | <font color= | | bgcolor="yellow" | 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; <font color=red>Julie</font> will work with Saul and Beth on this. | ||
|- | |- | ||
! scope="row" | Documentation | ! scope="row" | Documentation | ||
| Release | | Release documentation created and published | ||
''Current criteria: | ''Current criteria: M4 schedule items completed'' | ||
| bgcolor=" | | bgcolor="#66FF33" | on-track | ||
|- | |- | ||
! scope="row" | Performance | ! scope="row" | Build Performance | ||
| | | Build performance targets achieved | ||
''Current criteria: Performance features are in master'' | ''Current criteria: Performance features are in master'' | ||
| bgcolor="yellow" | see [[Yocto 1.0 Schedule]]; | | bgcolor="yellow" | see [[Yocto 1.0 Schedule]]; one additional goal could be that the build completes in 90 minutes or less with a single socket desktop system. First, we need to get real build statistics to see if that is realistic to achieve given where we are in the schedule. <font color=red>Julie</font> to ask Jaijun if he has statistics. | ||
|- | |- | ||
! scope="row" | Marketing requirements complete | ! scope="row" | Marketing requirements complete | ||
| Line 63: | Line 63: | ||
| bgcolor="white" | | | bgcolor="white" | | ||
|} | |} | ||
== Tunnel Creek BSP Release Criteria == | == Tunnel Creek BSP Release Criteria == | ||
Revision as of 23:44, 8 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. |
bug count is high; bug triage meetings will hopefully address |
| 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 performance targets achieved
Current criteria: Performance features are in master |
see Yocto 1.0 Schedule; one additional goal could be that the build completes in 90 minutes or less with a single socket desktop system. First, we need to get real build statistics to see if that is realistic to achieve given where we are in the schedule. Julie to ask Jaijun if he has statistics. |
| 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 | Both images are respun. Beth will package Tues 2/8/2011 |
| Open Bugs | All bugs dispositioned; Show-stoppers fixed | TBD based on testing of latest build |
| Functional Tests | 100% of planned tests executed | Tom will test final tarballs when available. Jaijun will test on Feb 10th. (Need to send note on his return.) |
| Legal Compliance | All legal requirements met | Plan in place to create click-through. Getting host set up. |
| Documentation | Release Notes created and published | Scott created a draft for Tom's review. |
| 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 |
