Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(505 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 7, 2020 ==
== Yocto Project Weekly Status Nov. 19th, 2024 ==
Current Dev Position: YP 3.1 M2 <br/>
Current Dev Position: YP 5.2 M1<br/>
Next Deadline: YP 3.1 M2 build date 1/20/2020<br/>
Next Deadline: YP 5.2 M1 Release date 2024-12-09<br/>


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1 M1 was released.
*YP 5.0.5 is under review
*Over the last two weeks there were a number of significant fixes for hash equivalence which should resolve some of the long standing bugs reported here. Some of these fixes may require further architectural tweaks to the codebase but those are cleanups which can happen in due course now the root causes are identified.
*YP 4.0.23 is in QA
*There are performance issues that remain in hashequivlence but these will be looked at only once the correctness issues and intermittent test failures are addressed.
*Patch merging is continuing to flow but there are a lot of upgrades pending after the recent AUH run.
*There are some puzzling selftest failures that remain, in particular a locked signatures one which seems to be caused through bad interaction with the hash equivalence code but is intermittent and does not make sense.
*A patch is pending to remove support for BB_DANGLINGAPPENDS_WARNONLY
*The patch queue for master should be roughly up to date which some key changes such as the gettext upgrade having merged recently. Some pending changes like the glibc upgrade look problematic.
*Yocto Project Compatible (and hence yocto-check-layer) is potentially undergoing some small tweaks which includes checking for SECURITY files in repository top levels, checking for network access outside do_fetch as part of normal builds and checking for disabled QA checks.  
*A key functionality change has merged this week where the layout of the sstate directory has changed. This was done to try and improve performance and handle some performance issues where the previous code simply wasn’t scaling. There is no user visible impact but it does mean new sstate will be generated into a new layout and the older sstate will be ignored. The sstate filename length issues should also be addressed by this patchset.
*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
*Whilst the SWAT process is disbanded, the effect of this is that Richard now has to file the bugs personally. This distracts from other things that could be worked on.
*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 triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.
*The 5.2 development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
*The TSC is working on LTS plans, productive discussions have been had and a new policy on handling this and stable releases should be available in the coming weeks.
*We need to continue to develop this, thanks to all who have contributed so far!
*We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.1 M2 build date 1/20/2020
*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 3.1 M2 release date 1/31/2020
*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
*YP 3.1 M3 build date 2/24/2020
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*YP 3.1 M3 release date 3/6/2020
*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
*YP 3.1 M4 build date  3/30/2020
*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.
*YP 3.1 M4 release date  4/24/2020
*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.3 build date  2/10/2020
*WDD 2721 (last week 2759) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 2.7.3 release date 2/21/2020
*OE-Core/Poky Patch Metrics
*YP 3.0.2 build date  2/3/2020
**Total patches found: 1077 (last week 1070)
*YP 3.0.2 release date 2/14/2020
**Patches in the Pending State: 178 (17%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/


'''Tracking Metrics:'''<br/>
'''YP 5.2 Milestone Dates:'''<br/>
*WDD 2773 (last week 2783) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.2 M1 Build Date 2024-12-09
*Poky Patch Metrics 
*YP 5.2 M1 Release Date 2024-12-20
**Total patches found: 1400 (last week 1400)
*YP 5.2 M2 Build Date 2025-01-20
**Patches in the Pending State: 562 (40%) [last week 561 (40%)]
*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:'''<br/>
*YP 5.0.5 is in review.
*YP 4.0.23 is in QA.
*YP 4.0.23 Release Date 2024-11-29
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 45: 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]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]

Latest revision as of 15:43, 19 November 2024

Yocto Project Weekly Status Nov. 19th, 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 is under review
  • YP 4.0.23 is in QA
  • Patch merging is continuing to flow but there are a lot of upgrades pending after the recent AUH run.
  • A patch is pending to remove support for BB_DANGLINGAPPENDS_WARNONLY
  • Yocto Project Compatible (and hence yocto-check-layer) is potentially undergoing some small tweaks which includes checking for SECURITY files in repository top levels, checking for network access outside do_fetch as part of normal builds and checking for disabled QA checks.
  • 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 is in review.
  • YP 4.0.23 is in QA.
  • YP 4.0.23 Release Date 2024-11-29
  • 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=86498"