Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status June 11, 2019 ==
== Yocto Project Weekly Status June 18, 2019 ==
Current Dev Position: YP 2.8 M2<br/>
Current Dev Position: YP 2.8 M2<br/>
Next Deadline:  YP 2.8 Milestone 2 Cutoff July 14th, 2019<br/>
Next Deadline:  YP 2.8 Milestone 2 Cutoff July 14th, 2019<br/>
Line 5: Line 5:
'''SWAT Team Rotation:'''<br/>
'''SWAT Team Rotation:'''<br/>


*SWAT lead is currently: Anuj
*SWAT lead is currently: Paul
*SWAT team rotation: Anuj -> Paul on June 14, 2019
*SWAT team rotation: Paul -> Ross on June 21, 2019
*SWAT team rotation: Paul -> Ross on June 21, 2019
*SWAT team rotation: Ross -> Amanda on June 28, 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 13th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday June 20th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday July 2nd 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 9th July at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*2.8 M1 has been built and rc2 is now undergoing QA (rc1 ran into an issue with a broken autobuilder worker).
*2.8 M1 has been through QA and is waiting on responses from YP TSC members on release readiness. It had more issues that would be ideal but most were relatively minor and are being worked upon, several with known causes now with fixes in master. As such its likely to be released.
*Stephen continues to be unavailable, please refer any queries to Richard
*Stephen is recovering from the accident and will now respond to emails. We’re pleased to have him back and wish him a continued speedy recovery!
*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 proving to be a tricky subject. Some people are having trouble with emails not making it to the lists which we recognise is a serious issue. Equally, our groups.io plan isn’t proving workable without major user visible change due to the current domain structure we have. *It is being worked on as a priority to find a way forward.
*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
*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.
*We’re grateful to Sandy, WindRiver and Michael for helping get patchtest back into operation. Its tests are looking like they could do with a little improvement but it is catching some issues and great to see progress with it again.
*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.
*During M2 Richard plans to look into our options for changing runqueue to better support more advanced sstate usage. This may have an impact on how quickly patches merge as the work there is involved and needs focus.
*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.
*We’d like to remind people that where test suites exist, we’d appreciate it if people would run them before they send patches, e.g. “oe-selftest -r devtool” or “oe-selftest -r wic”.
*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/>
*M1 Cutoff June 9th
*M1 is built and out of QA
*M1 Release June 21st
*M2 Cutoff 14th July
*M2 Cutoff 14th July
*M2 Release 26th July
*M2 Release 26th July
Line 37: Line 35:


'''Planned upcoming dot releases:'''<br/>
'''Planned upcoming dot releases:'''<br/>
*YP 2.6.3 (Thud) is in planning
*YP 2.7.1 (Warrior) is planned for build imminently now that 2.8 M1 is done
*YP 2.7.1 (Warrior) is in planning
*YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and before 2.8 M2


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


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

Revision as of 21:18, 18 June 2019

Yocto Project Weekly Status June 18, 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 through QA and is waiting on responses from YP TSC members on release readiness. It had more issues that would be ideal but most were relatively minor and are being worked upon, several with known causes now with fixes in master. As such its likely to be released.
  • Stephen is recovering from the accident and will now respond to emails. We’re pleased to have him back and wish him a continued speedy recovery!
  • Mailing lists are proving to be a tricky subject. Some people are having trouble with emails not making it to the lists which we recognise is a serious issue. Equally, our groups.io plan isn’t proving workable without major user visible change due to the current domain structure we have. *It is being worked on as a priority to find a way forward.
  • 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 grateful to Sandy, WindRiver and Michael for helping get patchtest back into operation. Its tests are looking like they could do with a little improvement but it is catching some issues and great to see progress with it again.
  • During M2 Richard plans to look into our options for changing runqueue to better support more advanced sstate usage. This may have an impact on how quickly patches merge as the work there is involved and needs focus.
  • We’d like to remind people that where test suites exist, we’d appreciate it if people would run them before they send patches, e.g. “oe-selftest -r devtool” or “oe-selftest -r wic”.

Planned Releases for YP 2.8:

  • M1 is built and out of QA
  • 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.7.1 (Warrior) is planned for build imminently now that 2.8 M1 is done
  • YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and before 2.8 M2

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=54029"