Attendees: Dave. Nitin, Beth, Jessica, Mark, Darren, Terrance, Richard, Saul, ScottR, Denys, Josh, Matthew M3 readiness - release criteria review (https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.2_Status#Milestone_3 ): 1. Functional completion: All P1s but 1145 and 1890 are completed. 1145 and 1890 have been pushed to M4 due to resource conflict with conferences and their preparation. 1145 is about improve bitbake output messaging. 1890 is about the web interface for build history analysis. They are both pushed to early M4. There are no features depending on them. The team agrees that they can be left for M4. a significant part of P2/P3's are completed in M3 or close to complete. We also moved some of the P2/P3's to post 1.2. We are still reviewing the list, there will be more to be moved to post 1.2. 2. No high bugs against M3. All high bugs are analyzed and they are not blockers for M3 release. 2066 is a high bug without any fix now. But it does not affect P1 features of M3 release. We have a plan and Saul will follow up to root cause it and have the fix in master. 3. The full pass QA report looks good. We have some issues with the core build system but most of them have patches in master already. 2048: patches soon, marked for M4 2050: Bruce/Nitin has a patch already, needs to be in master. Marked for M4 2054: Patch in master 1229: Patch in master 2051: Patch in master 2052: Patch in master 4. Distro tested with latest version and they all passed. 5. There is no significant performance degradation. 2048: patches soon, marked for M4 2050: Bruce/Nitin has a patch already, needs to be in master. Marked for M4 2054: Patch in master 1229: Patch in master 2051: Patch in master 2052: Patch in master Decision: the team unanimously agreed to release M3 RC1 for M3. Beth will pack up the release and release note, it should be released sometime today. 1.1.1 point release: We had a build and QA has given a full pass testing for it. Some issues are found, we have fixed significant ones and pulled the patches into the build. QA has tested and verified those fixes. We still have some issues left but the team agrees that they should not block the point release. Decision: the team agrees to release the current build for the 1.1.1 point release. Next step: 1. Beth will pack up the release. 2. Josh will gather the known issues list and send to Beth. 3. Scott Rifenbark will work with Beth to point the 1.1.1 web link to the right place. 4. Beth will then push and announce the release in the public mailing list.
-----Original Appointment----- From: Liu, Song Sent: Friday, March 09, 2012 2:44 PM To: [email protected] Cc: Mueller, Robert; 'Ravi Vompolu'; 'Anders Darander'; Barros Pena, Belen; Bodke, Kishore K; 'Bruce Ashfield'; 'Daniel Cauchy'; 'deVries, Alex'; 'Dixon, Brad'; Dmytriyenko, Denys; Erway, Tracey M; Flanagan, Elizabeth; Hart, Darren; 'Hatle, Mark'; 'Jeremy Puhlman'; Kooi, Koen; Kridner, Jason; Li, Susie; '[email protected]'; Lock, Joshua; 'McCombe, Kevin'; Moeller, Thorsten; '[email protected]'; Osier-mixon, Jeffrey; '[email protected]'; 'Polk, Jeffrey'; Purdie, Richard; 'Ranslam, Rob'; Rifenbark, Scott M; Saxena, Rahul; Stewart, David C; Wang, Shane; Wold, Saul; Yu, Ke; Zanussi, Tom; Zhang, Jessica; 'Hudson, Sean'; Arce Moreno, Abraham; [email protected]; Elizabeth Flanagan; Moses, Fred Subject: Yocto Project 1.2 M3 & 1.1.1 release readiness When: Monday, March 12, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: Bridge Info Enclosed Monday, March 12, 2012, 08:00 AM US Pacific Time 916-356-2663, 8-356-2663, Bridge: 4, Passcode: 1137217 Speed dialer: inteldialer://4,1137217 | Learn more _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
