Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(471 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status November 12, 2019 ==
== Yocto Project Weekly Status April 16th, 2024 ==
Current Dev Position: YP 3.1 M1 <br/>
Current Dev Position: YP 5.0 preparing to build rc2 <br/>
Next Deadline: YP 3.1 M1 build Dec. 2, 2019<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>
 
'''SWAT Team Rotation:'''<br/>
*SWAT lead is currently: Anuj
*SWAT team rotation: Anuj -> Chen on Nov. 15, 2019
*SWAT team rotation: Chen > Paul on Nov. 22, 2019
*://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Nov. 14th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday April 11th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Dec. 3rd at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday April 9th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Nov. 12th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - See https://www.twitch.tv/theyoctojester
*Twitch - Next event is Tuesday Nov. 12th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.7.2 is still undergoing QA
*YP 5.0 rc1 is building but has many (6+) failures in the build so will have to be abandoned.
*There were some key fixes for pseudo related issues which mean it continues to work with modern distros like Fedora 31.
*The final dunfell build will follow 5.0 into QA.
*Patches have continued to merge and master is staying roughly current with the pending patch queue but there continue to be recurring build failures that are not being addressed.
*The master branch has diverged from scarthgap.
*The YP TSC worked on and shared a proposal on how an LTS release could work which is available at: https://docs.google.com/document/d/1AwAFDf52f_FoXksbHEVUMlu4hpcI0JMGVG-Kj_sUkyc/ . There has been much discussion about this, patience would be appreciated as the TSC and governing board work through this to come up with plans on how we proceed.
*For 5.0, we were able to switch to the new hash equivalence server however the need for websockets complicated the worker configuration and needed new buildtools tarball versions which are causing various problems.
*We have begun collecting ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
*During the rc1 build as well as pip and setuptools issues within buildtools, we also saw a qemuppc boot issue, an instance of the spdx dependency problem, an sstate mirror issue and a github network error. This highlights how important fixing these is over the release cycle. The volume of these may impact our ability to maintain the LTS.
*If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+Stephen.
*Thanks to everyone who sent documentation patches, we’re in much better shape with the migration guide and release notes now. Further improvements are still very welcome.
*The “Binary Distro” work is now well underway and there are PR Server passthrough and image testing patches under review. The wiki page has had a number of policy/process proposals documented, help is welcome to help improve these, or highlight where further documentation is needed.
*There are patches for improving the build performance graphs in review. Sample output from the changes is here and here.
*There are also patches under review for the patch/cve metrics page to improve the usability.
*We continue to watch the NIST NVD (CVE database) situation, the recent update didn’t clarify much. Unfortunately there doesn’t appear to be a clear path forward as yet but using data directly from MITRE may help give partial information. These issues are making it hard to know what to include in the 5.0 release as it isn’t clear which changes are security related.
 
'''Ways to contribute:'''<br/>
*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!
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There are bugs that are currently unassigned for YP 5.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_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.
 
'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 is building
*YP 5.0 M4 Release date 2024/04/30
 
'''YP 5.1 Proposed Milestone Dates:'''<br/>
*YP 5.1 M1 Build date 2024-05-20
*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


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1 M1 Proposed build date 12/2/2019
*YP 4.3.4 is released.
*YP 3.1 M1 Proposed release date 12/13/2019
*YP 3.1.33 build date 2024-04-15
*YP 3.1 M2 Proposed build date 1/20/2020
*YP 3.1.33 Release date 2024-04-26
*YP 3.1 M2 Proposed release date 1/31/2020
*YP 4.0.18 build date 2024-04-22
*YP 3.1 M3 Proposed build date 2/24/2020
*YP 4.0.18 Release date 2024-05-03
*YP 3.1 M3 Proposed release date 3/6/2020
*YP 4.0.19 build date 2024-06-03
*YP 3.1 M4 Proposed build date 3/30/2020
*YP 4.0.19 Release date 2024-06-14
*YP 3.1 M4 Proposed release date 4/24/2020


'''Planned upcoming dot releases:'''<br/>
'''Upcoming Proposed dot releases:'''<br/>
*YP 3.0.1 has patches being queued in poky-contrib
*YP 5.0.1 Build Date 2024-05-13
*YP 2.7.2 (Warrior) is in QA.
*YP 5.0.1 Release Date 2024-05-24
*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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2508 (last week 2518) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2719 (last week 2696) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1445 (last week 1446)
**Total patches found: 1173 (last week 1174)
**Patches in the Pending State: 579 (40%) [last week 579 (40%)]
**Patches in the Pending State: 249 (21%) [last week 249 (21%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''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 47: Line 83:


== 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:37, 16 April 2024

Yocto Project Weekly Status April 16th, 2024

Current Dev Position: YP 5.0 preparing to build rc2
Next Deadline: 1st April 2024 YP 5.0 M4 build

Next Team Meetings:

Key Status/Updates:

  • YP 5.0 rc1 is building but has many (6+) failures in the build so will have to be abandoned.
  • The final dunfell build will follow 5.0 into QA.
  • The master branch has diverged from scarthgap.
  • For 5.0, we were able to switch to the new hash equivalence server however the need for websockets complicated the worker configuration and needed new buildtools tarball versions which are causing various problems.
  • During the rc1 build as well as pip and setuptools issues within buildtools, we also saw a qemuppc boot issue, an instance of the spdx dependency problem, an sstate mirror issue and a github network error. This highlights how important fixing these is over the release cycle. The volume of these may impact our ability to maintain the LTS.
  • Thanks to everyone who sent documentation patches, we’re in much better shape with the migration guide and release notes now. Further improvements are still very welcome.
  • The “Binary Distro” work is now well underway and there are PR Server passthrough and image testing patches under review. The wiki page has had a number of policy/process proposals documented, help is welcome to help improve these, or highlight where further documentation is needed.
  • There are patches for improving the build performance graphs in review. Sample output from the changes is here and here.
  • There are also patches under review for the patch/cve metrics page to improve the usability.
  • We continue to watch the NIST NVD (CVE database) situation, the recent update didn’t clarify much. Unfortunately there doesn’t appear to be a clear path forward as yet but using data directly from MITRE may help give partial information. These issues are making it hard to know what to include in the 5.0 release as it isn’t clear which changes are security related.

Ways to contribute:

YP 5.0 Milestone Dates:

  • YP 5.0 is building
  • YP 5.0 M4 Release date 2024/04/30

YP 5.1 Proposed Milestone Dates:

  • YP 5.1 M1 Build date 2024-05-20
  • 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.3.4 is released.
  • YP 3.1.33 build date 2024-04-15
  • YP 3.1.33 Release date 2024-04-26
  • YP 4.0.18 build date 2024-04-22
  • YP 4.0.18 Release date 2024-05-03
  • YP 4.0.19 build date 2024-06-03
  • YP 4.0.19 Release date 2024-06-14

Upcoming Proposed dot releases:

  • YP 5.0.1 Build Date 2024-05-13
  • YP 5.0.1 Release Date 2024-05-24
  • 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

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