[yocto] Notes: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PDT) ([e-mail])

[Jolley, Stephen K]

The notes are at google doc: https://docs.google.com/document/d/15jB6nUJU2wrtnu6w07L9RZpNlj6AoxSTPEX5aELts1g/edit?usp=sharing and pasted below. If you want access to the link, please request access.


Attendees: Armin, Stephen, Joshua, Randy, Amanda, Lewis, Jon, Tim, Mark, Nick, Alejandro, Richard, Michael, Tracey, Rich, Ross,
Proposed release schedule for YP 2.7 timeframe. We discussed and agreed these were reasonable.

Milestone Start YMD Cutoff YMD Release YMD Working Days
YP 2.4.4 2018/6/12 2018/11/5 2018/11/16 146
YP 2.5.2 2018/8/16 2018/11/19 2018/11/30 95
YP 2.7 M1 2018/10/29 2018/12/10 2018/12/21 42
YP 2.7 M2 2018/12/10 2019/01/21 2019/02/01 42
YP 2.6.1 2018/10/26 2019/01/07 2019/01/18 59
YP 2.7 M3 2019/01/21 2019/02/25 2019/03/08 35
YP 2.7 M4 2019/02/25 2019/04/01 2019/04/26 35
YP 2.5.3 2018/11/19 2019/05/10 2019/05/21 161
YP 2.6.2 2019/02/15 2019/05/24 2019/06/04 130

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

Discussed testing numbering scheme. The current numbers map to the Testopia test case, but we are getting rid of Testopia, so the current numbers don’t have good meaning anymore.

Discussed that a new patch Richard has sent, will break up the ptest tests into individual test and give individual results for each test. Do we want to separate endurance/stress tests from functional tests. Currently they are either disabled or not. Currently no capability exists to make these tests just occasional tests, not on or off.

Note: that in YP 2.7 and later, most manual testing will not happen until some level of automation is developed to do this testing.

YP 2.6 M4 rc1 is in QA, 95% completed, and the current status can be viewed at: https://wiki.yoctoproject.org/wiki/index.php?title=WW44_-_2018-10-30_-_Full_Test_Cycle_2.6_M4_RC1

Discussed with the number of CVE’s that have come out since YP 2.6 was built, do we want to do an rc2. Decided to release and add known CVE’s to the release notes.

Discussed the transition of QA from Intel to the community. Progress is being made.

Discussed the length of time for QA, it was 3-4 days and is now more like 2 weeks.

Discussed bisecting poky, need to validate it is still able to be done. Randy will do so.

Ran through and discussed the proposed ideas for YP 2.7, adding a few below.

AR: Stephen - Set up extra meeting for 11/27 to continue discussion.
AR All – Please review the below items and start creating Bugzilla items for them.

Ideas for 2.7:
• Python 3.7 [RP, Ross, Alejandro]
• Perl recipe cleanup/upgrade (5.28.0)? [RP] - work in progress here https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavin/perl-sanity (AlexK)
• systemd default for poky, needs autobuilder changes. [RP, Kai Kang]
• Other poky specific config to nodistro?
• Revise autobuilder test matrix [RP]
o Ptest
o Kernel
o Add multiconfig buildset to AB
o meta-cgl?
o meta-oe?
o YP plat member layers (intel/TI)
• Revise release artifacts [RP]
• Capability to run ‘make check’ using qemu user-mode for all packages? [Ross]
• NFS rootfs in test automation {AK}
• Sstate Hash equivalence (don’t rebuild on gcc patch) {Joshua Watt}
• Switch to memres bitbake by default? [RP]
• Rust? [Ross]
• qemuarm rename to qemuarmv5 and change to v7 as default {Jon Mason}
• Switch qemuarm to qemu -m virt rather than versatilepb {Jon Mason}
• Containers: Agree on what belongs in oe-core vs other layers [Randy]
• Virgl support in qemu {AlexK} (JaMa is now upstreaming this from webos, I believe)
• Multiconfig SDK [Alejandro]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
• Cell: [phone]
• Email: ***@intel.com