Yocto Project v1.1 Release Criteria: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(→‎Yocto Project 1.1: added status for April 26th)
(→‎Yocto Project 1.0.1: added status from 26-Apr)
Line 32: Line 32:


= Yocto Project 1.0.1 =  
= Yocto Project 1.0.1 =  
The Yocto Project 1.0.1 release will contain critical bug fixes from Yocto Project 1.0.  The exact content of this release still needs to be determined.
The Yocto Project 1.0.1 release will contain critical bug fixes from Yocto Project 1.0.


{| border="1" {{table}}
{| border="1" {{table}}
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Target''' || ! scope="col" bgcolor="grey" | '''Status'''
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Target''' || ! scope="col" bgcolor="grey" | '''Status'''
|-
|-
| Functional Completion || No new significant features are added.  Any minor functionality added is documented in git logs. ||
| Functional Completion || No new significant features are added.  Any minor functionality added is documented in git logs. || bgcolor="yellow" | There are 300 commits that Richard is looking through to pull for 1.0.1.
|-
|-
| Build and Release (Yocto) || 1.0.1 build can be built with no errors. || Build will run May 14th to May 21st.
| Build and Release (Yocto) || 1.0.1 build can be built with no errors. || bgcolor="yellow" | Build will run May 14th to May 21st.  Beth will run a test build the week of May 10th.  She has a plan that doesn't require getting new hardware to do.
|-
|-
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || Build will run May 14th to May 21st.
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || bgcolor="yellow" | Build will run May 14th to May 21st.  Beth will run a test build the week of May 10th.  She has a plan that doesn't require getting new hardware to do.
|-
|-
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="yellow"| 17 bugs exist for 1.0.1 so far; need to finish dispositioning by April 25th (May 5th is last date)
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="yellow" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.0%20PointRelease 20 bugs] exist for 1.0.1 so far; triage team will disposition to ensure we have the right list.
|-
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || First test pass will be May 21st-22nd (weekly).  Go/No-Go will determine if full test pass should be done.
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || First test pass will be May 21st-22nd (weekly).  Go/No-Go will determine if full test pass should be done.

Revision as of 18:13, 26 April 2011

The Release Criteria for the various Yocto Project 1.1 releases are below.

Yocto Project 1.1

Release Criteria Milestone 1 Target Milestone 1 Status
Functional Completion All M1 features and BSPs are in the build. see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for status
Build and Release (Yocto) All M1 features can be built with no errors. OE rename has caused temporary instability in builds. Beth will try a new build in the next week.
Build and Release (BSPs) Core and meta-intel BSPs can be built with no errors. BSPs haven't been building right. Beth will work with Tom on this.
Open Bugs All bugs have been dispositioned. High issues have been fixed. NEW bugs
HIGH priority bugs
Action Item: Saul will assign some of Richard's NEW bugs to the correct owners. Action Item: Julie will send the team a reminder about the NEW bugs. Action Item: Bruce will check with his team about bugs 414 and 609. Action Item: Saul will check with Dexuan about bug 828. 828 hasn't been looked at in a month.
Functional Tests 100% of planned tests are executed and results are logged in bugzilla. Julie to check with Jiajun.
BSP Testing 100% of planned tests are executed and results are logged in bugzilla. Julie to check with Jiajun.
Alpha N/A for M1 N/A
Documentation M1 documentation deliverables are complete. Julie to check with Scott.
Build Performance Plan for improving performance is defined. Will wait until Richard returns for details.
Upstream Commits Have upstream status updated on 90% of patches (so that we can have a status update) We will have status in at least 90% of the patches. It may be status = "pending."
Marketing Deliverables Giveaway plans defined Julie/Darren/Tracey are working on a giveaway plan.
Publication M1 release is announced

Yocto Project 1.0.1

The Yocto Project 1.0.1 release will contain critical bug fixes from Yocto Project 1.0.

Release Criteria Target Status
Functional Completion No new significant features are added. Any minor functionality added is documented in git logs. There are 300 commits that Richard is looking through to pull for 1.0.1.
Build and Release (Yocto) 1.0.1 build can be built with no errors. Build will run May 14th to May 21st. Beth will run a test build the week of May 10th. She has a plan that doesn't require getting new hardware to do.
Build and Release (BSPs) BSPs targeted for 1.0.1 (= all current BSPs) are built. Build will run May 14th to May 21st. Beth will run a test build the week of May 10th. She has a plan that doesn't require getting new hardware to do.
Open Bugs All bugs targeted for 1.0.1 are in the build by May 13th. 20 bugs exist for 1.0.1 so far; triage team will disposition to ensure we have the right list.
Functional Tests 100% of planned tests are executed and results are logged in bugzilla. First test pass will be May 21st-22nd (weekly). Go/No-Go will determine if full test pass should be done.
BSP Testing 100% of planned tests are executed and results are logged in bugzilla. First test pass will be May 21st-22nd (weekly). Go/No-Go will determine if full test pass should be done.
Documentation 1.0.1 Release Notes are complete. Release notes to begin May 14th.
Build Performance 1.0.1 does not increase performance above 107 minutes on a developer machine.
Publication 1.0.1 release is built and announced to the community.