Yocto Project v1.0 Release Criteria: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
== Yocto v1.0 Release Criteria ==
{| border="1"
{| border="1"
|+ Yocto v1.0 Release Criteria
|+ Release Criteria
! scope="col" | Release Criteria  
! scope="col" | Release Criteria  
! scope="col" | Target
! scope="col" | Target
Line 8: Line 9:
| All M1, M2, M3 functional features implemented by EO M3
| All M1, M2, M3 functional features implemented by EO M3
''Current Criteria:  Functional features are ready to go into master.''
''Current Criteria:  Functional features are ready to go into master.''
| bgcolor="yellow" | see [[Yocto 1.0 Schedule]]
| bgcolor="yellow" | see [[Yocto 1.0 Schedule#Stabilization Phase Features and Activities]]
|-
|-
! scope="row" | Build and Release
! scope="row" | Build and Release
Line 64: Line 65:




== Tunnel Creek BSP Release Criteria ==


{| border="1"
{| border="1"
|+ Tunnel Creek BSP Release Release Criteria
|+ Release Criteria
! scope="col" | Release Criteria  
! scope="col" | Release Criteria  
! scope="col" | Target
! scope="col" | Target
Line 105: Line 107:




== Laverne Point Release Criteria ==


{| border="1"
{| border="1"
|+ Laverne Point Release Release Criteria
|+ Release Criteria
! scope="col" | Release Criteria  
! scope="col" | Release Criteria  
! scope="col" | Target
! scope="col" | Target

Revision as of 22:02, 8 February 2011

Yocto v1.0 Release Criteria

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.

have many changes left to merge into master
Build and Release

(BSPs)

Yocto BSPs build reliably

Current criteria: Plan in place to build/QA BSPs by EO Feb.

Beth/Saul created a solution to have the infrastructure by Feb 11th.
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

Need tag on alpha code
Documentation Release Notes created and published

Current criteria: None yet

Performance Performance targets achieved

Current criteria: Performance features are in master

see Yocto 1.0 Schedule; Action Item: Saul: take first cut at performance metrics
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
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
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