Le mar. 13 janv. 2026 à 16:55, Stephen Jolley via lists.openembedded.org <
[email protected]> a écrit :

> Current Dev Position:YP 6.0 M1
>
> Next Deadline: YP 6.0 M1 Build Date 2026-01-05
>
> Next Team Meetings:
>
>    -
>
>    Bug Triage meeting - Thursday 15th Jan. 7:30am PDT (
>    https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
>    -
>
>    Weekly Project Engineering Sync  - Tuesday 13th Jan. 8am PDT (
>    https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
>    <https://zoom.us/j/990892712>
>    -
>
>    Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday
>    19th Jan. 9am PDT (
>    https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1
>    <https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1>)
>
>
> Project data dashboard: https://dashboard.yoctoproject.org/
>
> Key Status/Updates:
>
>    -
>
>    YP 5.0.15 is under review.
>    -
>
>    YP 5.3.1 is in QA
>    -
>
>    YP 6.0 M1 will build when the 5 open high bugs are resolved.
>    -
>
>    There are also 4 high bugs open for 6.0 M2.
>    -
>
>    We are seeing multiple serious issues blocking 6.0 M1 from building:
>    -
>
>       A glibc test causing builds to hang (a buffer overflow SIGABRT in
>       unfs3 triggered by host compiler + fortify source) (#16113)
>       -
>
>       Hangs of the autobuilder controller (database locking, should be
>       fixed) (#16129)
>       -
>
>       Issues with a CVE patch applied to tar in
>       rocky9/alma9/centos-stream using the openat2 syscall which pseudo 
> doesn’t
>       wrap (#16117)
>       -
>
>       Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on
>       older systems (patchelf triggered?) (#16074, #16087)
>       -
>
>       still need to disable the npm fetcher (#16105)
>       -
>
>    We have not had this number of high bugs blocking releases in several
>    years
>    -
>
>    The number of intermittent failures affecting stable release builds is
>    becoming problematic. Any given build is now statistically likely to hit
>    one or more of them and we don’t have successful builds. Since we struggle
>    to get help in addressing these, we need to change and start potentially
>    blocking releases (including stable/LTS) until these get addressed in some
>    way. We plan to form a dedicated team to investigate these and find ways of
>    removing the failures from our builds which may include reducing testing.
>    -
>
>    To be clear, due to the problems above, most patch testing is now
>    stalled as the autobuilder is currently inoperable and we can’t test
>    anything.
>    -
>
>    The project is exploring the idea of applying for funding for security
>    related work. If anyone (individual or consultancies) has ideas, please
>    talk to Paul/Richard/TSC. This is an opportunity to work on those issues
>    you never have time/funding for!
>
>
> Want to contribute? We would appreciate help with the following areas:
>
>    -
>
>    We have several open issues for pseudo and limited maintainer time to
>    work on them. Help from someone familiar with systems programming in C
>    would be greatly appreciated.
>    
> https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
>    -
>
>    There are a large number of intermittent failures on our autobuilder,
>    any help with investigating, reproducing or solving these issues would be
>    welcome! https://valkyrie.yocto.io/pub/non-release/abint/
>    -
>
>    Many recipes in openembedded-core would benefit from a new recipe
>    maintainer. Please look at
>    
> https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc
>    and see if you can adopt any of the unassigned recipes.
>    -
>
>    For more ways to contribute, see
>    
> https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
>
>
> New to the project?
>
>    -
>
>    We have a list of issues we think are good places to start
>    contributing:
>    https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
>
>
> Tracking Metrics:
>
>    -
>
>    WDD 3026 (last week 3011) (
>    https://wiki.yoctoproject.org/charts/combo.html)
>    -
>
>    OE-Core/Poky Patch Metrics
>    -
>
>       Total patches found: 1089 (last week 1092)
>       -
>
>       Patches in the Pending State: 151 (14%) [last week 151 (14%)]
>       -
>
>       https://autobuilder.yocto.io/pub/non-release/patchmetrics/
>
>
> YP 6.0 Milestone Dates:
>
>    -
>
>    YP 6.0 M1 Build Date 2026-01-05
>    -
>
>    YP 6.0 M1 Release Date 2026-01-16
>    -
>
>    YP 6.0 M2 Build Date 2026-02-02
>    -
>
>    YP 6.0 M2 Release Date 2026-02-13
>    -
>
>    YP 6.0 M3 Build Date 2026-03-02
>    -
>
>    YP 6.0 M3 Release Date 2026-03-13
>    -
>
>    YP 6.0 M4 Build Date 2026-03-30
>    -
>
>    YP 6.0 M4 Release Date 2026-04-26
>
>
> Upcoming dot releases:.
>
>    -
>
>    YP 5.0.15 is under review.
>    -
>
>    YP 5.3.1 is in QA.
>    -
>
>    YP 4.0.33 Build Date 2026-01-26
>    -
>
>    YP 4.0.33 Release Date 2026-01-30
>
>
Hello,

There is only 4 days between build date and release date for 4.0.33.
That is far less than the usual 11 days. isn't this a problem?

Regards,


>    -
>
>    YP 5.0.16 Build Date 2026-02-09
>    -
>
>    YP 5.0.16 Release Date 2026-02-20
>    -
>
>    YP 5.3.2 Build Date 2026-02-16
>    -
>
>    YP 5.3.2 Release Date 2026-02-27
>    -
>
>    YP 4.0.34 Build Date 2026-02-23
>    -
>
>    YP 4.0.34 Release Date 2026-03-06
>    -
>
>    YP 5.3.3 Build Date 2026-03-09
>    -
>
>    YP 5.3.3 Release Date 2026-03-20
>    -
>
>    YP 5.0.17 Build Date 2026-03-16
>    -
>
>    YP 5.0.17 Release Date 2026-03-23
>    -
>
>    YP 4.0.35 Build Date 2026-04-06
>    -
>
>    YP 4.0.35 Release Date 2026-04-17
>    -
>
>    YP 5.3.4 Build Date 2026-04-13
>    -
>
>    YP 5.3.4 Release Date 2026-04-24
>    -
>
>    YP 5.0.18 Build Date 2026-04-20
>    -
>
>    YP 5.0.18 Release Date 2026-05-01
>    -
>
>    YP 5.0.19 Build Date 2026-05-26
>    -
>
>    YP 5.0.19 Release Date 2026-06-05
>
>
> 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]>*
>
> 
>
>

-- 
Yoann Congal
Smile ECS
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#229279): 
https://lists.openembedded.org/g/openembedded-core/message/229279
Mute This Topic: https://lists.openembedded.org/mt/117245166/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to