Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status June 4, 2019 ==
== Yocto Project Weekly Status June 11, 2019 ==
Current Dev Position: YP 2.8 M1<br/>
Current Dev Position: YP 2.8 M2<br/>
Next Deadline:  YP 2.8 Milestone 1 Cutoff June 9th, 2019<br/>
Next Deadline:  YP 2.8 Milestone 2 Cutoff July 14th, 2019<br/>


'''SWAT Team Rotation:'''<br/>
'''SWAT Team Rotation:'''<br/>


*SWAT lead is currently: Chen
*SWAT lead is currently: Anuj
*SWAT team rotation: Armin -> Anuj on June 7, 2019
*SWAT team rotation: Anuj -> Paul on June 14, 2019
*SWAT team rotation: Anuj -> Paul on June 14, 2019
*SWAT team rotation: Paul -> Ross on June 21, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday June 6th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday June 13th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday June 4th at 8am PDT (https://zoom.us/j/990892712)  
*Monthly Project Meeting Tuesday July 2nd at 8am PDT (https://zoom.us/j/990892712)  
*Twitch - Next event is Tuesday 11th June at 8am PDT (https://www.twitch.tv/yocto_project)
*Twitch - Next event is Tuesday 11th June at 8am PDT (https://www.twitch.tv/yocto_project))


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*2.8 M1 is nearly upon us with just under a week left for the remaining features/patches.
*2.8 M1 has been built and rc2 is now undergoing QA (rc1 ran into an issue with a broken autobuilder worker).
*Stephen continues to be unavailable, please refer any queries to Richard
*Stephen continues to be unavailable, please refer any queries to Richard
*Mailing lists are moving to groups.io instead of our current mailman setup. This shouldn’t impact users directly, more details will be sent to the mailing lists before the transfer. THe Yocto Project lists will move first, followed by OE, likely a week later.
*Mailing lists are moving to groups.io instead of our current mailman setup. This shouldn’t impact users directly, more details will be sent to the mailing lists before the transfer. THe Yocto Project lists will move first, followed by OE, likely a week later.
*We have a new “newcomer” bug category which are bugs suited to someone new to the project. These can be seen here: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*We have a new “newcomer” bug category which are bugs suited to someone new to the project. These can be seen here: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*Uninative 2.5 was released which supports gcc 9. This should fix issues for fedora 30 builds and allow the bringup of fedora 30 workers in the autobuilder too.
*We’re seeing an increasing number of intermittent failures which affect the autobuilder builds, causing problems for merging patches and for release builds. One cause, a long standing problem with gpg signing testing has finally been root caused and fixed. Several others keep appearing. There is a backlog of them in the bugzilla and we’re opening bugs for the new ones.
*ARM native builds are now working on the autobuilder as well as KVM accelerated ARM ptest and ltp testing.
*M1 isn’t of ideal quality, there are three ptest timeouts (2.7 had none). The ptest failure rate is however much improved. There is nobody actively working on some of the ptest timeout issues so holding the milestone build wouldn’t have made much difference but its a worrying sign for the project quality.
*There are ongoing concerns about perl module dependencies. Tim and Richard have applied bandaids to solve some ptest issues but we really need work in this area if there are any perl experts interested.
*M1 also has a couple of MIPS issues with the gcc9 upgrade. There doesn’t appear to be much interest in investigating and fixing these which raises questions about supporting the architecture within the project.
*Many further ptests fixes have merged, thanks to all for the contributions.
*There was a Yocto Project related article in LWN: https://lwn.net/Articles/788626/


'''Planned Releases for YP 2.8:'''<br/>
'''Planned Releases for YP 2.8:'''<br/>
Line 41: Line 41:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2507 (last week 2524) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 1478 (last week 2507) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1513 (last week 1525)
**Total patches found: 1507 (last week 1513)
**Patches in the Pending State: 646 (43%) [last week 649 (43%)]
**Patches in the Pending State: 641 (43%) [last week 646 (43%)]


'''Key Status Links for YP:'''<br/>
'''Key Status Links for YP:'''<br/>

Revision as of 14:43, 11 June 2019

Yocto Project Weekly Status June 11, 2019

Current Dev Position: YP 2.8 M2
Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

SWAT Team Rotation:

Next Team Meetings:

Key Status/Updates:

  • 2.8 M1 has been built and rc2 is now undergoing QA (rc1 ran into an issue with a broken autobuilder worker).
  • Stephen continues to be unavailable, please refer any queries to Richard
  • Mailing lists are moving to groups.io instead of our current mailman setup. This shouldn’t impact users directly, more details will be sent to the mailing lists before the transfer. THe Yocto Project lists will move first, followed by OE, likely a week later.
  • We have a new “newcomer” bug category which are bugs suited to someone new to the project. These can be seen here: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
  • We’re seeing an increasing number of intermittent failures which affect the autobuilder builds, causing problems for merging patches and for release builds. One cause, a long standing problem with gpg signing testing has finally been root caused and fixed. Several others keep appearing. There is a backlog of them in the bugzilla and we’re opening bugs for the new ones.
  • M1 isn’t of ideal quality, there are three ptest timeouts (2.7 had none). The ptest failure rate is however much improved. There is nobody actively working on some of the ptest timeout issues so holding the milestone build wouldn’t have made much difference but its a worrying sign for the project quality.
  • M1 also has a couple of MIPS issues with the gcc9 upgrade. There doesn’t appear to be much interest in investigating and fixing these which raises questions about supporting the architecture within the project.
  • There was a Yocto Project related article in LWN: https://lwn.net/Articles/788626/

Planned Releases for YP 2.8:

  • M1 Cutoff June 9th
  • M1 Release June 21st
  • M2 Cutoff 14th July
  • M2 Release 26th July
  • M3 Cutoff (Feature Freeze) 25th Aug
  • M3 Release 6th Sept
  • M4 Cutoff 30th Sept
  • 2.8 (M4) Final Release 25th Oct


Planned upcoming dot releases:

  • YP 2.6.3 (Thud) is in planning
  • YP 2.7.1 (Warrior) is in planning

Tracking Metrics:

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=53658"