Yocto Project v1.0 Release Criteria

From Yocto Project
Revision as of 18:04, 22 February 2011 by Jnfleisc (talk | contribs) (updates from Feb 22 Yocto meeting)
Jump to navigationJump to search

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

Richard will send a note regarding the four open features.

Build and Release

(Yocto)

Yocto 1.0 code builds reliably

Current criteria: All features in master can be built.

There are two major items blocking stable builds:

- Docutils is failing - Saul will discuss with Scott G today. - Zypper is failing <- Richard is working with Qing. We have until Friday to get these fixed.

Build and Release

(BSPs)

Yocto BSPs build reliably

Current criteria: BSPs are built for testing.

Goals for this release are met. QA will be able to test BSPs at the same time as RC1.
Open Bugs All bugs dispositioned; Show-stoppers fixed

Current criteria: All bugs have been dispositioned.

65 bugs not yet dispositioned (in "New" state); Owners: Tom, Scott, Saul, Richard, Qing, Paul, Nitin, Mark, Ke, Julie, Josh, Jeff, Edwin, Darren, Dongxiao); one Critical/High - bug 734; six Major/High
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

on-track
BSP Testing 100% of planned BSP tests executed

Current criteria: BSPs are tested at least once during master stabilization

on-track
Alpha Feedback Alpha feedback included

Current criteria: Alpha begins Feb 11th and completes Feb 23rd

testing nearing completion; positive feedback so far
Documentation Release documentation created and published

Current criteria: M4 schedule items completed

Yocto_1.0_Schedule#Documentation_Deliverables
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: Richard and PRC team complete performance analysis.

Team is down to 97-98 minute builds. Richard will continue the analysis/tweak cycle; however, attention needs to go to other areas as well this week. File dependencies is one other low-hanging fruit item Richard would like to investigate.
Marketing requirements complete Engineering requirements to the marketing plan are complete

Current criteria: Yocto demo is prepared for ELC.

PPC no longer available for Joshua - investigating backup options. Need videos. Need plexiglass boxes. Coding effort underway, but not complete.
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 Build completed
Open Bugs All bugs dispositioned; Show-stoppers fixed Only minor bugs found (724, 725)
Functional Tests 100% of planned tests executed Tom tested. Jiajun will test Thursday.
Legal Compliance All legal requirements met Account is set up for click-through. Click-through team has info they need.
Documentation Release Notes created and published Scott/Tom are finalizing and things look good.
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
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_v1.0_Release_Criteria&oldid=799"