Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 10: Line 10:


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.5 M1 is due to build this week
*YP 3.5 M1 is in QA
*YP 3.4.1 is likely to be released this week
*YP 3.1.13 is due to build this week
*There were some changes to the yocto-check-layer script to verify more of the contents of README files which has led to improvements in a number of layer README files.
*We have maintenance to the autobuilder planned to fit SSDs to speed up IO and update the host distros to more modern equivalents. If parts arrive as planned, this is scheduled for next week (20th-24th) and the autobuilder will be unavailable during the work. There may be bring up issues with the new distros.
*The Yocto Project Summit and OpenEmbedded Developer virtual meetings last week seemed successful, thanks to the organizers and presenters for their hard work and presentations and everyone who attended to make it a success.
*There were significant improvements in patch metrics this week with large drops in both patches in the pending state and overlap number of patches. Thanks to everyone who contributed to that!
*We have continued to audit a number of the patches in OE-Core with the removal of quite a number of obsolete patches and a number being submitted to the appropriate upstreams. This will result in an improvement to the quality of the core layer and make general maintenance easier going forward. Any help, particularly from those with knowledge of specific areas or upstreams would be most welcome.
*As part of patch cleanup, some changes were made which could impact other layers or our spectrum of support. The libtool prefix patches were dropped as the need was largely obsolete by recipe specific sysroots, hosttools and other developments and this may mean patches in other layers can be dropped too. Some non-upstream invasive mips and sh4 patches were dropped as they were either obsolete or there were less invasive ways to handle them.  
*We continue to see a reduction in the number of patches in the “Pending” state. Many thanks to everyone who has taken the time to review patch status and handle accordingly, particularly where they were accepted upstream. This will significantly benefit the project in the long term.
*CVE metrics improved this week with drops in open CVEs for both dunfull and master.
*Intermittent issues continue to rise and help is very much welcome on these issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
*Intermittent issues continue to rise and help is very much welcome on these issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
*SWAT handling of autobuilder issues has sadly not been functioning correctly for the last couple of weeks with a large backlog of untriaged issues.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>

Revision as of 15:43, 14 December 2021

Yocto Project Weekly Status Dec.14th, 2021

Current Dev Position: YP 3.5 M1
Next Deadline: 6th Dec. 2021 YP 3.5 M1 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.5 M1 is in QA
  • YP 3.1.13 is due to build this week
  • We have maintenance to the autobuilder planned to fit SSDs to speed up IO and update the host distros to more modern equivalents. If parts arrive as planned, this is scheduled for next week (20th-24th) and the autobuilder will be unavailable during the work. There may be bring up issues with the new distros.
  • There were significant improvements in patch metrics this week with large drops in both patches in the pending state and overlap number of patches. Thanks to everyone who contributed to that!
  • As part of patch cleanup, some changes were made which could impact other layers or our spectrum of support. The libtool prefix patches were dropped as the need was largely obsolete by recipe specific sysroots, hosttools and other developments and this may mean patches in other layers can be dropped too. Some non-upstream invasive mips and sh4 patches were dropped as they were either obsolete or there were less invasive ways to handle them.
  • CVE metrics improved this week with drops in open CVEs for both dunfull and master.
  • Intermittent issues continue to rise and help is very much welcome on these issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

Ways to contribute:

YP 3.5 Milestone Dates:

  • YP 3.5 M1 in QA
  • YP 3.5 M1 Release date 2021/12/17
  • YP 3.5 M2 build date 2022/01/10
  • YP 3.5 M2 Release date 2022/1/21
  • YP 3.5 M3 build date 2022/2/21
  • YP 3.5 M3 Release date 2022/03/04
  • YP 3.5 M4 build date 2022/04/04
  • YP 3.5 M4 Release date 2022/04/29

Upcoming dot releases:

  • YP 3.4.1 is released
  • YP 3.1.13 build date 2021/12/13
  • YP 3.1.13 Release date 2021/12/22
  • YP 3.1.14 build date 2022/01/24
  • YP 3.1.14 Release date 2022/02/04
  • YP 3.4.2 build date 2022/02/07
  • YP 3.4.2 Release date 2022/02/18
  • YP 3.3.5 build date 2022/02/14
  • YP 3.3.5 Release date 2022/02/25
  • YP 3.1.15 build date 2022/03/14
  • YP 3.1.15 Release date 2022/03/25
  • YP 3.4.3 build date 2022/03/21
  • YP 3.4.3 Release date 2022/04/01
  • YP 3.3.6 build date 2022/03/28
  • YP 3.3.6 Release date 2022/04/08
  • YP 3.1.16 build date 2022/04/25
  • YP 3.1.16 Release date 2022/05/06

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives

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