Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(575 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status February 26, 2019 ==
== Yocto Project Weekly Status Nov. 26th, 2024 ==
Current Dev Position: YP 2.7 M3 <br/>
Current Dev Position: YP 5.2 M1<br/>
Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019<br/>
Next Deadline: YP 5.2 M1 Release date 2024-12-09<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Nov. 28th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Nov. 26th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester


*SWAT lead is currently: Ross
'''Key Status/Updates:'''<br/>
*SWAT team rotation: Ross -> Chen on Mar. 1, 2019
*YP 5.0.5 was released.
*SWAT team rotation: Chen -> Armin on Mar. 8, 2019
*YP 4.0.23 is in under review.
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*Patch merging is continuing to flow but there are a lot of upgrades pending that were recently posted.
*BB_DANGLINGAPPENDS_WARNONLY was removed.
*yocto-check-layer is now checking for SECURITY files and there are changes planned for increasing the QA checks tested for.
*The yocto-testresults repository was reworked and the commits recreated to avoid problems with the size of the repository. The log files were separated to an http share here: https://valkyrie.yocto.io/pub/non-release/testresult-logarchives/
*These changes pose a question/challenge for the stable branches. The changes mean we should avoid breaking git mirroring.
*As a result of this work, the reproducible builds summary page now functions much faster.
*Several performance tweaks were made for bitbake pipe handling for large amounts of log data to avoid slow ptest builds and hangs.
*A potential new “include_all” conf file directive (discussed on the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2055 ) has no strong objections and is proceeding to proof of concept
*There are patches under review for the addition of configuration fragment management to bitbake. It does require the addition of support for ‘/’ characters in variable flag names (which has been requested in the past too).
*The 5.2 development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
*We need to continue to develop this, thanks to all who have contributed so far!


'''Key Status/Updates:'''<br/>
'''Ways to contribute:'''<br/>
*We have now passed the feature freeze point for 2.7
*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!
*YP 2.7 M2 rc2 is out of QA and being readied for release.  See: https://wiki.yoctoproject.org/wiki/WW07_-_2019-02-14_-_Full_Test_Cycle_2.7_M2_RC2 and https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status#Milestone_2_-_Target_Feb._1.2C_2019
*There is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
*We now have resulttool, buildhistory and build-performance all working with the autobuilder and will be using this as the primary QA mechanism going forward. More details can be found here:
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
http://lists.openembedded.org/pipermail/openembedded-architecture/2019-February/001591.html
*There are bugs that are currently unassigned for YP 5.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_Unassigned_Enhancements/Bugs
*There were some serious usability issues found with multiconfig, those have been fixed in master and thud.
*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.
*Various recipe upgrades made it in, thanks to all who contributed. Several recipes also converted to meson including glib-2.0 and gdk-pixbuf.
*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.
*We now need to build M3 as we’re past feature freeze point for 2.7. Right now we’re aware of the following things which ideally need to be resolved first:
*Help us resolve CVE issues: CVE metrics
**Bug 13178 “X server and matchbox desktop don't start up properly on beaglebone” needs to be fixed
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
**Find the framebuffer problem with qemuarmv7 and switch to that
**Several ptest issues would be addressed (missing openssl tests, 3 timeouts)
**Arm build host issues identified and resolved
*It’s unlikely we’ll switch to virtgl by default for 2.7 due to lack of testing from the community although the base patches for this have merged.


'''Planned Releases for YP 2.7:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 2.7 M2 rc2 is out of QA.
*WDD 2736 (last week 2721) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 2.7 M2 Release Target was Feb. 1, 2019
*OE-Core/Poky Patch Metrics
*YP 2.7 M3 Cutoff is Feb. 25, 2019
**Total patches found: 1073 (last week 1077)
*YP 2.7 M3 Release Target is Mar. 8, 2019
**Patches in the Pending State: 178 (17%) [last week 178 (17%)]
*YP 2.7 M4 Cutoff is Apr. 1, 2019
*https://autobuilder.yocto.io/-release/patchmetrics/
*YP 2.7 M4 Release Target is Apr. 26, 2019


'''Planned upcoming dot releases:'''<br/>
'''YP 5.2 Milestone Dates:'''<br/>
*YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*YP 5.2 M1 Build Date 2024-12-09
*YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*YP 5.2 M1 Release Date 2024-12-20
*YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.
*YP 5.2 M2 Build Date 2025-01-20
*YP 5.2 M2 Release Date 2025-01-31
*YP 5.2 M3 Build Date 2025-03-03
*YP 5.2 M3 Release Date 2025-03-14
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2415 (last week 2392) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.5 was released.
*Poky Patch Metrics 
*YP 4.0.23 is in review.
**Total patches found: 1516 (last week 1527)
*YP 5.1.1 Build Date 2024-12-02
**Patches in the Pending State: 660 (44%) [last week 663 (43%)]
*YP 5.1.1 Release Date 2024-12-13
*YP 5.0.6 Build Date 2024-12-16
*YP 5.0.6 Release Date 2024-12-27
*YP 4.0.24 Build Date 2025-01-06
*YP 4.0.24 Release Date 2025-01-17
*YP 5.1.2 Build Date 2025-01-13
*YP 5.1.2 Release Date 2025-01-24
*YP 5.0.7 Build Date 2025-01-27
*YP 5.0.7 Release Date 2025-02-07
*YP 4.0.25 Build Date 2025-02-17
*YP 4.0.25 Release Date 2025-02-28
*YP 5.1.3 Build Date 2025-02-24
*YP 5.1.3 Release Date 2025-03-07
*YP 5.0.8 Build Date 2025-03-10
*YP 5.0.8 Release Date 2025-03-21
*YP 5.1.4 Build Date 2025-03-24
*YP 5.1.4 Release Date 2025-04-04
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.26 Release Date 2025-04-18
*YP 5.0.9 Build Date 2025-04-21
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.0.10 Build Date 2025-06-02
*YP 5.0.10 Release Date 2025-06-13
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11


'''Key Status Links for YP:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features<br/>


== 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]]

Latest revision as of 15:52, 26 November 2024

Yocto Project Weekly Status Nov. 26th, 2024

Current Dev Position: YP 5.2 M1
Next Deadline: YP 5.2 M1 Release date 2024-12-09

Next Team Meetings:

Key Status/Updates:

  • YP 5.0.5 was released.
  • YP 4.0.23 is in under review.
  • Patch merging is continuing to flow but there are a lot of upgrades pending that were recently posted.
  • BB_DANGLINGAPPENDS_WARNONLY was removed.
  • yocto-check-layer is now checking for SECURITY files and there are changes planned for increasing the QA checks tested for.
  • The yocto-testresults repository was reworked and the commits recreated to avoid problems with the size of the repository. The log files were separated to an http share here: https://valkyrie.yocto.io/pub/non-release/testresult-logarchives/
  • These changes pose a question/challenge for the stable branches. The changes mean we should avoid breaking git mirroring.
  • As a result of this work, the reproducible builds summary page now functions much faster.
  • Several performance tweaks were made for bitbake pipe handling for large amounts of log data to avoid slow ptest builds and hangs.
  • A potential new “include_all” conf file directive (discussed on the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2055 ) has no strong objections and is proceeding to proof of concept
  • There are patches under review for the addition of configuration fragment management to bitbake. It does require the addition of support for ‘/’ characters in variable flag names (which has been requested in the past too).
  • The 5.2 development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
  • We need to continue to develop this, thanks to all who have contributed so far!

Ways to contribute:

  • 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 is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
  • 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.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_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.

Tracking Metrics:

YP 5.2 Milestone Dates:

  • YP 5.2 M1 Build Date 2024-12-09
  • YP 5.2 M1 Release Date 2024-12-20
  • YP 5.2 M2 Build Date 2025-01-20
  • YP 5.2 M2 Release Date 2025-01-31
  • YP 5.2 M3 Build Date 2025-03-03
  • YP 5.2 M3 Release Date 2025-03-14
  • YP 5.2 M4 Build Date 2025-03-31
  • YP 5.2 M4 Release Date 2025-04-25

Upcoming dot releases:

  • YP 5.0.5 was released.
  • YP 4.0.23 is in review.
  • YP 5.1.1 Build Date 2024-12-02
  • YP 5.1.1 Release Date 2024-12-13
  • YP 5.0.6 Build Date 2024-12-16
  • YP 5.0.6 Release Date 2024-12-27
  • YP 4.0.24 Build Date 2025-01-06
  • YP 4.0.24 Release Date 2025-01-17
  • YP 5.1.2 Build Date 2025-01-13
  • YP 5.1.2 Release Date 2025-01-24
  • YP 5.0.7 Build Date 2025-01-27
  • YP 5.0.7 Release Date 2025-02-07
  • YP 4.0.25 Build Date 2025-02-17
  • YP 4.0.25 Release Date 2025-02-28
  • YP 5.1.3 Build Date 2025-02-24
  • YP 5.1.3 Release Date 2025-03-07
  • YP 5.0.8 Build Date 2025-03-10
  • YP 5.0.8 Release Date 2025-03-21
  • YP 5.1.4 Build Date 2025-03-24
  • YP 5.1.4 Release Date 2025-04-04
  • YP 4.0.26 Build Date 2025-04-07
  • YP 4.0.26 Release Date 2025-04-18
  • YP 5.0.9 Build Date 2025-04-21
  • YP 5.0.9 Release Date 2025-05-02
  • YP 4.0.27 Build Date 2025-05-19
  • YP 4.0.27 Release Date 2025-05-30
  • YP 5.0.10 Build Date 2025-06-02
  • YP 5.0.10 Release Date 2025-06-13
  • YP 4.0.28 Build Date 2025-06-30
  • YP 4.0.28 Release Date 2025-07-11

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