Attendees:  Paul, Tom, Julie, Saul, Darren, Mark, Richard, Dennis, Jessica, 
Dave, Joshua

The Yocto Technical Team held a Go/No-Go for the current 1.0.1 release.  The 
decision was "no-go" due to needing to add and test the fix to bug 1029 and 
needing to investigate and address/test bug 1087.  Both bugs were found during 
the 1.0.1 test pass.  Details below.

1)      Review Yocto 1.0.1 Release Criteria
Team reviewed criteria at:  
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.0.1_Release_Criteria.

Details:
Bug 909 - Team is comfortable with this issue possibly not being fixed for 
1.0.1 (It may be fixed, but we did not run compliance tests to know.)
Bug 1029 - Darren provided a fix yesterday.  Saul put into a consolidated pull 
request yesterday afternoon.  Not yet in master.  Once it hits master, Saul 
will move it into Bernard.  He will create a build for just a Bernard 
Beagleboard image for QA to test.  QA will run through the full Beagleboard 
test plan.  No other tests needed for this issue.
Action Item:  Julie:  Check that uboot is part of the test plan.

1087 - Saul will investigate.  The fix ranges from documentation to full build. 
 Tom will help Saul do runtime tests on his Crown Bay.
 
Team was okay with the fact that only weekly BSP testing was done for this 
release.  We may ask for full BSP testing for the next release if the Crown Bay 
fix warrants it.

Saul will start working on Release Notes for 1.0.1.  They will discuss resolved 
bugs and open issues remaining.

2)      Go/No-Go decision - No-Go
After this email, Richard will send the community a reply with location of 
current branch in case they want to use the fixes sooner.

3)      Discuss next steps (either release process or bug fix/rebuild/retest 
process, depending on results of go/no-go) and timeline

Bug 1029:
Richard will pull fix into master.
Saul will pull fix into Bernard.
Beth will build only Beagleboard for 1.0.1.
Jiajun will run through Beagleboard testing.

Bug 1087:
Saul will continue investigating.
Team will discuss results and next steps via email and finalize during the 
Technical Team meeting on Tuesday.

4) Opens
The QA team needs a Beagleboard XM not just Beagleboard C4.  Darren needs a 
Beagleboard C4.

Dennis noted that both can be purchased from Digikey.  Jason's program applies 
to both as well if that becomes an option.
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to