Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(495 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status September 17, 2019 ==
== Yocto Project Weekly Status June 11th, 2024 ==
Current Dev Position: YP 2.8 M4 Feature Freeze<br/>
Current Dev Position: YP 5.1 M2 <br/>
Next Deadline: YP 3.0 Final Release 25th Oct<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<br/>
 
'''SWAT Team Rotation:'''<br/>
*SWAT lead is currently: Paul
*SWAT team rotation: Ross -> Amanda on Sept. 20, 2019
*SWAT team rotation: Amanda -> Chen on Sept. 13, 2019
*://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Sept 19th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday June 13th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Oct. 1st at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday June 11th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Sept. 17th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - See https://www.twitch.tv/theyoctojester
*Twitch - Next event is Tuesday Oct. 8th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We’re now in feature freeze for 3.0 and working on bug fixing for final release
*YP 4.0.19 has been through QA and is due for release
*We have not built M3 yet as there are still three issues that need to be resolved:
*YP 5.1 M1 rc2 is in QA
**strace ptest regressions with 5.1/5.2 kernels
*RFC patches for the CVE tooling changes have been posted, help in review is appreciated
**systemd timeouts on mips
*There are SPDX 3.0 patches ready for review on the mailing list
**hashequiv server rewrite
*There are patches proposing that missing patch Upstream-Status entries be a fatal QA error, this is likely to merge soon as there have been no objections to it.
*The strace regressions will be discussed with the kernel community, the best workaround may be to lower the individual test timeouts so one the affected individual tests fail rather than all tests timing out.
*We have a fix for the final Fedora 40 issue, thanks Victor.
*The qemumips issue with systemd is puzzling as its happening in hwdb and hwdb should be generated in advance anyway. Investigation is ongoing about why its being regenerated, a workaround is to increase the timeout as mips is just slow (it does complete eventually, its just marginal).
*We appreciate everyone fixing layers to work with master after recent changes, the autobuilder health is looking greener, thanks!
*The hashequiv server changes are being tested in master-next
*The copy_unihashes function was dropped from bitbake after the locked signature file improvements which simplifies further tooling work
It is planned to build M3 this week with the workarounds mentioned above worst case. Its expected there would be further hashequiv fixing during M4.
*There is discussion on openembedded-architecture about the details around  configuration fragment tooling potentially being integrated into bitbake
*We hope to make up time during M4 by having M3 at high quality and take advantage of our automation.
*There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
*Documentation - Due to illness Scott is unavailable for the next month or two so doc patches will be handled by Richard or Ross in the short term. We’ll likely limit them to correctness issues and defer any substantial new text. If anyone has availability and skills to work on the manuals please talk to us. We’re aware there is a patch backlog.
*Please consider signing this to show support for those changes.
*If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+Stephen.
*Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
*Through post release upgrading our patch count reduced again and is now the lowest level since July 2008!


'''Planned Releases for YP 3.0 {2.8}:'''<br/>
'''Ways to contribute:'''<br/>
*M3 Release 6th Sept
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*M4 Cutoff 30th Sept - this will be YP 3.0.
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*YP 3.0 {2.8 (M4)} Final Release 25th Oct
*There are bugs that are currently unassigned for YP 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_Unassigned_Enhancements/Bugs
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
*Help is very much welcome in trying to resolve our autobuilder intermittent 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.
*Help us resolve CVE issues: CVE metrics
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''Planned upcoming dot releases:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 2.7.2 (Warrior) is planned for after YP 3.0 release.
*WDD 2774 (last week 2772) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 2.6.4 (Thud) is planned for after YP 2.7.2  release.
*OE-Core/Poky Patch Metrics
**Total patches found: 1072 (last week 1098)
**Patches in the Pending State: 205 (19%) [last week 205 (19%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''Tracking Metrics:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*WDD 2424 (last week 2424) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.1 M1 is in QA
*Poky Patch Metrics 
*YP 5.1 M1 Release date 2024-05-31
**Total patches found: 1417 (last week 1417)
*YP 5.1 M2 Build date 2024-07-08
**Patches in the Pending State: 582 (41%) [last week 582 (41%)]
*YP 5.1 M2 Release date 2024-07-19
*YP 5.1 M3 Build date 2024-08-26
*YP 5.1 M3 Release date 2024-09-06
*YP 5.1 M4 Build date 2024-09-30
*YP 5.1 M4 Release date 2024-10-25


'''Key Status Links for YP:'''<br/>
'''Upcoming dot releases:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status<br/>
*YP 4.0.19 is ready for release.
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule<br/>
*YP 5.0.2 Build Date 2024-06-24
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features<br/>
*YP 5.0.2 Release Date 2024-07-05
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.20 Release Date 2024-07-26
*YP 5.0.3 Build Date 2024-08-12
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.21 Build Date 2024-09-09
*YP 4.0.21 Release Date 2024-09-20
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.22 Release Date 2024-10-25
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.23 Release Date 2024-11-29


'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 53: Line 73:


== Archives ==
== Archives ==
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]

Revision as of 14:49, 11 June 2024

Yocto Project Weekly Status June 11th, 2024

Current Dev Position: YP 5.1 M2
Next Deadline: YP 5.1 M2 Build 8 July 2024

Next Team Meetings:

Key Status/Updates:

  • YP 4.0.19 has been through QA and is due for release
  • YP 5.1 M1 rc2 is in QA
  • RFC patches for the CVE tooling changes have been posted, help in review is appreciated
  • There are SPDX 3.0 patches ready for review on the mailing list
  • There are patches proposing that missing patch Upstream-Status entries be a fatal QA error, this is likely to merge soon as there have been no objections to it.
  • We have a fix for the final Fedora 40 issue, thanks Victor.
  • We appreciate everyone fixing layers to work with master after recent changes, the autobuilder health is looking greener, thanks!
  • The copy_unihashes function was dropped from bitbake after the locked signature file improvements which simplifies further tooling work
  • There is discussion on openembedded-architecture about the details around configuration fragment tooling potentially being integrated into bitbake
  • There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
  • Please consider signing this to show support for those changes.
  • Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
  • We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
  • Through post release upgrading our patch count reduced again and is now the lowest level since July 2008!

Ways to contribute:

Tracking Metrics:

YP 5.1 Milestone Dates:

  • YP 5.1 M1 is in QA
  • YP 5.1 M1 Release date 2024-05-31
  • YP 5.1 M2 Build date 2024-07-08
  • YP 5.1 M2 Release date 2024-07-19
  • YP 5.1 M3 Build date 2024-08-26
  • YP 5.1 M3 Release date 2024-09-06
  • YP 5.1 M4 Build date 2024-09-30
  • YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

  • YP 4.0.19 is ready for release.
  • YP 5.0.2 Build Date 2024-06-24
  • YP 5.0.2 Release Date 2024-07-05
  • YP 4.0.20 Build Date 2024-07-15
  • YP 4.0.20 Release Date 2024-07-26
  • YP 5.0.3 Build Date 2024-08-12
  • YP 5.0.3 Release Date 2024-08-23
  • YP 4.0.21 Build Date 2024-09-09
  • YP 4.0.21 Release Date 2024-09-20
  • YP 5.0.4 Build Date 2024-09-23
  • YP 5.0.4 Release Date 2024-10-04
  • YP 4.0.22 Build Date 2024-10-14
  • YP 4.0.22 Release Date 2024-10-25
  • YP 5.0.5 Build Date 2024-11-11
  • YP 5.0.5 Release Date 2024-11-22
  • YP 4.0.23 Build Date 2024-11-18
  • YP 4.0.23 Release Date 2024-11-29

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