Current Dev Position: YP 5.0 M3 - Feature Freeze

Next Deadline: 19th February 2024 YP 5.0 M3 build

Next Team Meetings:

   -

   Bug Triage meeting Thursday March 7th at 7:30 am PST (
   https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
   -

   Weekly Project Engineering Sync Tuesday March 5th at 8 am PST (
   https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
   <https://zoom.us/j/990892712>
   -

   Twitch -  See https://www.twitch.tv/theyoctojester


Key Status/Updates:

   -

   We are now at feature freeze for 5.0, preparing to build M3
   -

   YP 4.3.3 was released
   -

   YP 3.1.32 is in QA
   -

   Several changes have merged for M3:
   -

      genericarm64 machine (also added to autobuilder)
      -

      go upgrade to 1.21.7
      -

      rust upgrade to 1.75
      -

      change to bmaptool hosting
      -

      using ipk to generate poky-altcfg images with extra space added
      -

      6.6.20 stable kernel update
      -

      ability to use “extratools” on autobuilder for tests (e.g.
      imagemagick components)
      -

   Changes still needed or under consideration
   -

      genericarm64 helper artefacts publishing changes
      -

      QA screenshot comparison
      -

      sstate permissions issue testcase
      -

      go upgrade to 1.22 (tests cleanly on oe-core now, concerns for other
      layers)
      -

   We are seeing some odd failures, there was a devtool selftest failure
   (bug 15418 filed) and also an opkg lock issue as we enabled ipk images but
   that hasn’t recurred (yet). The opkg lock issue has been seen in builds by
   Khem previously.
   -

   There is a concerning problem when trying to update the CVE database
   since CPE restrictions don’t always update when changed upstream. This is
   causing higher numbers of CVEs to be reported on the autobuilder generated
   charts.
   -

   There have been questions about official RISC-V support in this next
   release, especially since it is an LTS. We will trial qemuriscv64 support
   in M3 but remove it before the final LTS release as there is no sponsor for
   that support.


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 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
   <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
   -

   We have a growing number of bugs in bugzilla, any help with them is
   appreciated.
   -

   Regarding bugs, even if you can’t fix a bug, submitting a failing test
   case that can reproduce the issue significantly improves the chances it
   might get fixed.


YP 5.0 Milestone Dates:

   -

   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:

   -

   YP 4.3.3 was released.
   -

   YP 3.1.32 is in QA.
   -

   YP 3.1.32 Release date 2024/03/15
   -

   YP 4.0.17 build date 2024/03/11
   -

   YP 4.0.17 Release date 2024/03/22
   -

   YP 4.3.4 build date 2024/03/25
   -

   YP 4.3.4 Release date 2024/04/05
   -

   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


Tracking Metrics:

   -

   WDD 2618 (last week 2633) (
   https://wiki.yoctoproject.org/charts/combo.html)
   -

   OE-Core/Poky Patch Metrics
   -

      Total patches found: 1155 (last week 1144)
      -

      Patches in the Pending State: 249 (22%) [last week 250 (22%)]
      -

   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:

https://wiki.yoctoproject.org/wiki/TSC

The Status reports are now stored on the wiki at:
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on this
weekly status update, let us know!]

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(    *Cell*:                (208) 244-4460

* *Email*:                 *s
<[email protected]>[email protected] <[email protected]>*
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196636): 
https://lists.openembedded.org/g/openembedded-core/message/196636
Mute This Topic: https://lists.openembedded.org/mt/104746788/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to