Yocto Project v1.0 Release Criteria

From Yocto Project
Revision as of 20:59, 7 February 2011 by Jnfleisc (talk | contribs)
Jump to navigationJump to search
Yocto v1.0 Release Criteria
Release Criteria Target Status
Development Progress All M1, M2, M3 features implemented by EO M3

Current Criteria: Features are ready to go into master.

see Yocto 1.0 Schedule
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

Current criteria: Weekly testing is performed on master

testing starts in Feb
BSP Testing 100% of planned BSP tests executed

Current criteria: TBD - pending BSP plan

Legal Compliance All legal requirements met

Current criteria: Legal review Feb 22nd

in progress
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 enhancement code in master

TBD
Publication Release and documentation are published on yoctoproject.org

Current criteria: None for this stage


Tunnel Creek BSP Release 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 built. Beth is creating final tarballs.
Open Bugs All bugs dispositioned; Show-stoppers fixed in progress - removable media issue will be documented as bug and logged in Release Notes. Fix is available. Do we want to include, rebuild, retest?
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. Text defined.
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 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 on-track