Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(84 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status October 24th, 2023 ==
== Yocto Project Weekly Status Nov. 19th, 2024 ==
Current Dev Position: YP 4.3 M4 (Feature Freeze)<br/>
Current Dev Position: YP 5.2 M1<br/>
Next Deadline: 2nd October 2023 YP 4.3 M4 build date<br/>
Next Deadline: YP 5.2 M1 Release date 2024-12-09<br/>


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


'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday October 26th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday October 24th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester
<br/>
'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*The YP 4.3 (M4) rc2 is in QA.
*YP 5.0.5 is under review
*For the 4.3 release, the 6.5 serial port issues caused the rc1 build to fail. That combined with a serious patchtest behavior meant we rebuilt and submitted an rc2 to QA. There were several abandoned builds due to infrastructure issues. We are now using the upstream kernel serial fix.
*YP 4.0.23 is in QA
*Our release branch (nanbield) and master have now diverged to keep the patch backlog under control so development patches are merging to master.
*Patch merging is continuing to flow but there are a lot of upgrades pending after the recent AUH run.
*Patchtest work is progressing and we’re nearly at the point where it will be replying live to emails on list. Examples of the responses can be seen on our test mailing list: https://lists.yoctoproject.org/g/test-list .
*A patch is pending to remove support for BB_DANGLINGAPPENDS_WARNONLY
*Source mirroring and reproducibility testing for meta-openembedded are now available on the project autobuilder.
*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.  
*The project is now strongly suggesting source code repositories have a SECURITY.md file to ensure users know what to do if they encounter a security issue. We are trying to ensure all key project repositories contain these. Patches are welcome and we’re encouraging all maintainers to follow this best practice.
*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
*The layer index has seen development work to ensure it uses secure components, can handle changes in practice (such as main branches), can illustrate Yocto Project Compatible status and that the errors/warnings generated from builds are under control. Thanks Tim!
*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).
*After consultation and discussions the project is now about to document its security processes to complete the work in this area. Please watch the mailing lists such as the architecture list if you have an interest in this area.
*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!
<br/>


'''Ways to contribute:'''<br/>
'''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: patchtest, layerindex, 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!
*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 identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There are bugs that are currently unassigned for YP 4.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_Unassigned_Enhancements.2FBugs
*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.
*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 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.
Line 30: Line 29:
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''Tracking Metrics:'''<br/>
*WDD 2721 (last week 2759) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1077 (last week 1070)
**Patches in the Pending State: 178 (17%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 4.3 Milestone Dates:'''<br/>
'''YP 5.2 Milestone Dates:'''<br/>
*YP 4.3 M3 was released.
*YP 5.2 M1 Build Date 2024-12-09
*YP 4.3 M4 build date  2023/10/02
*YP 5.2 M1 Release Date 2024-12-20
*YP 4.3 M4 Release date 2023/10/27
*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.0 Milestone Dates:'''<br/>
*YP 5.2 M3 Release Date 2025-03-14
*YP 5.0 M1 build date 2023/12/04
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.0 M1 Release date 2023/12/15
*YP 5.2 M4 Release Date 2025-04-25
*YP 5.0 M2 build date  2024/01/15
*YP 5.0 M2 Release date 2024/01/24
*YP 5.0 M3 build date  2024/02/19
*YP 5.0 M3 Release date 2024/03/01
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 Release date 2024/04/30
 


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.29 build date 2023/10/30
*YP 5.0.5 is in review.
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.23 is in QA.
*YP 4.0.14 build date 2023/11/06
*YP 4.0.23 Release Date 2024-11-29
*YP 4.0.14 Release date 2023/11/17
*YP 5.1.1 Build Date 2024-12-02
*YP 4.2.4 build date 2023/11/13
*YP 5.1.1 Release Date 2024-12-13
*YP 4.2.4 Release date 2023/11/24
*YP 5.0.6 Build Date 2024-12-16
*YP 4.3.1 build date 2023/11/27
*YP 5.0.6 Release Date 2024-12-27
*YP 4.3.1 Release date 2023/12/08
*YP 4.0.24 Build Date 2025-01-06
*YP 3.1.30 build date 2023/12/11
*YP 4.0.24 Release Date 2025-01-17
*YP 3.1.30 Release date 2023/12/22
*YP 5.1.2 Build Date 2025-01-13
*YP 4.0.15 build date 2023/12/18
*YP 5.1.2 Release Date 2025-01-24
*YP 4.0.15 Release date 2023/12/29
*YP 5.0.7 Build Date 2025-01-27
*YP 4.3.2 build date 2024/01/08
*YP 5.0.7 Release Date 2025-02-07
*YP 4.3.2 Release date 2024/01/19
*YP 4.0.25 Build Date 2025-02-17
*YP 3.1.31 build date 2024/01/22
*YP 4.0.25 Release Date 2025-02-28
*YP 3.1.31 Release date 2024/02/02
*YP 5.1.3 Build Date 2025-02-24
*YP 4.0.16 build date 2024/01/29
*YP 5.1.3 Release Date 2025-03-07
*YP 4.0.16 Release date 2024/02/09
*YP 5.0.8 Build Date 2025-03-10
*YP 4.3.3 build date 2024/02/12
*YP 5.0.8 Release Date 2025-03-21
*YP 4.3.3 Release date 2024/02/23
*YP 5.1.4 Build Date 2025-03-24
*YP 3.1.32 build date 2024/03/04
*YP 5.1.4 Release Date 2025-04-04
*YP 3.1.32 Release date 2024/03/15
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.17 build date 2024/03/11
*YP 4.0.26 Release Date 2025-04-18
*YP 4.0.17 Release date 2024/03/22
*YP 5.0.9 Build Date 2025-04-21
*YP 4.3.4 build date 2024/03/25
*YP 5.0.9 Release Date 2025-05-02
*YP 4.3.4 Release date 2024/04/05
*YP 4.0.27 Build Date 2025-05-19
*YP 3.1.33 build date 2024/04/15
*YP 4.0.27 Release Date 2025-05-30
*YP 3.1.33 Release date 2024/04/26
*YP 5.0.10 Build Date 2025-06-02
*YP 4.0.18 build date 2024/04/22
*YP 5.0.10 Release Date 2025-06-13
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.19 build date 2024/06/03
*YP 4.0.28 Release Date 2025-07-11
*YP 4.0.19 Release date 2024/06/14
 
 
'''Tracking Metrics:'''<br/>
*WDD 2475 (last week 2478) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1174 (last week 1176)
**Patches in the Pending State: 253 (22%) [last week 254 (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 95: Line 83:


== Archives ==
== Archives ==
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 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"