Yocto Project v1.1 Release Criteria: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(→‎Yocto Project 1.0.1: added resolved bugs to query)
(→‎Yocto Project 1.1: added 3-May status)
Line 6: Line 6:
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''
|-
|-
| Functional Completion || All M1 features and BSPs are in the build. || bgcolor="yellow" | "see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for status<br>Questions on Calendar: Is our M1 release plan correct? Who will add events and vacations?
| Functional Completion || All M1 features and BSPs are in the build. || bgcolor="yellow" | "see https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule for status<br>We need to ensure our release process for the milestones is clearly defined. Beth/Jiajun/Julie will discuss.
"
"
|-
|-
| Build and Release (Yocto) || All M1 features can be built with no errors. || bgcolor="orange" | OE rename has caused temporary instability in builds.  Beth will try a new build in the next week.<br>Question on M1 stabilize:  When can QA begin testing?
| Build and Release (Yocto) || All M1 features can be built with no errors. || bgcolor="orange" | Beth is fixing autobuilder config and will rebuild today.  She will also kick off Bernard on master-bernard.<br>QA can begin testing afterwards.
|-
|-
| Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="orange" | BSPs haven't been building right.  Beth will work with Tom on this.
| Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="orange" | Beth is fixing autobuilder config and will rebuild today.  She will also kick off Bernard on master-bernard.<br>QA can begin testing afterwards.
|-
|-
| Open Bugs || All bugs have been dispositioned.  High issues have been fixed. || bgcolor="orange" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&target_milestone=1.1 NEW bugs]<br>[http://bugzilla.yoctoproject.org/buglist.cgi?priority=High&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.1 HIGH priority bugs]<br>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.
| Open Bugs || All bugs have been dispositioned.  High issues have been fixed. || bgcolor="orange" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&target_milestone=1.1 NEW bugs]<br>[http://bugzilla.yoctoproject.org/buglist.cgi?priority=High&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.1 HIGH priority bugs]<br>Action  Item:  Saul will assign some of Richard's NEW bugs to the correct owners.  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.  Action Item:  Julie will send another email about the New bugs, and Saul will send one to the meta-data team.
|-
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || Not done?
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || Not done?
Line 28: Line 28:
|-
|-
| Publication || M1 release is announced ||
| Publication || M1 release is announced ||
|}
|}
 
= 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 Yocto Project 1.0.1 release will contain critical bug fixes from Yocto Project 1.0.

Revision as of 18:37, 3 May 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
We need to ensure our release process for the milestones is clearly defined. Beth/Jiajun/Julie will discuss.

"

Build and Release (Yocto) All M1 features can be built with no errors. Beth is fixing autobuilder config and will rebuild today. She will also kick off Bernard on master-bernard.
QA can begin testing afterwards.
Build and Release (BSPs) Core and meta-intel BSPs can be built with no errors. Beth is fixing autobuilder config and will rebuild today. She will also kick off Bernard on master-bernard.
QA can begin testing afterwards.
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: 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. Action Item: Julie will send another email about the New bugs, and Saul will send one to the meta-data team.
Functional Tests 100% of planned tests are executed and results are logged in bugzilla. Not done?
BSP Testing 100% of planned tests are executed and results are logged in bugzilla. Router station and PPC blocked
[mpc8315e-rdb & routerstationpro] minimal,sato,sato-sdk images boot failed (nightly build 20110423-1) http://bugzilla.pokylinux.org/show_bug.cgi?id=1006
Documentation M1 documentation deliverables are complete. No documentation deliverables exist for M1.
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, Jefro, 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. 17 bugs exist for 1.0.1 so far; triage team will disposition to ensure we have the right list.
30 bugs total
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.
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_v1.1_Release_Criteria&oldid=1559"