Current Dev Position: YP 4.2 M2

Next Deadline: 23rd January 2023 YP 4.2 M2 Build

 

Next Team Meetings:

*       Bug Triage meeting Thursday January 5th 7:30 am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*       Weekly Project Engineering Sync Tuesday January 3rd at 8 am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
*       Twitch -  See  <https://www.twitch.tv/theyoctojester>
https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*       YP 4.2 M1 and YP 4.0.6 were released.
*       Builds on the autobuilder are problematic at present due to
connection losses with the controller machine. We understand the cause and
will be migrating the controller to a new server/location in the next
maintenance window to address this.
*       A number of invasive bitbake changes have merged including a change
to add threading to bitbake's server/cooker. This will allow us to attempt
to resolve various UI/server hang related open bugs and to improve the user
experience, e.g. Ctrl+C handling. If people do see issues with hangs, please
report them and include the tail end of the bitbake-cookerdaemon.log file.
*       The bitbake cache changes to optionally include more hash debugging
information did merge. This currently triggers only for the bitbake -S
operations but once that mode is triggered for memory resident bitbake, it
is "sticky" and will remain set until it unloads. We have seen some OOM
issues on autobuilder workers which may be related to this, more debugging
is needed to check on bitbake's memory usage.
*       Automatic bitbake function library dependency code has also merged
and is active. This should let us migrate class code to become library code
for performance improvements.
*       A bug in the layer.conf variable changes was identified which was
causing re-parsing when it wasn't necessary. A fix has been merged to
address that.
*       The OE TSC decided in favour of adding export flag expansion despite
the performance impact so that patch will be queued.
*       We merged a number of neat rust improvements which add on target
cargo support and added automated QA tests for this functionality so we can
ensure it continues to work and doesn't regress. Thanks Alex Kiernan, we
hope to see more series like this one!
*       CVE levels in master have improved but still need a little work
*       The autobuilder maintenance window is moving from Friday to Monday.
*       We have a growing number of bugs in bugzilla, any help with them is
appreciated.

 

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: 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!
*       There are bugs identified as possible for newcomers to the project:
<https://wiki.yoctoproject.org/wiki/Newcomers>
https://wiki.yoctoproject.org/wiki/Newcomers
*       There are bugs that are currently unassigned for YP 4.2. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhan
cements.2FBugs
*       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/mai
ntainers.inc>
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.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>
https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
*       Help us resolve CVE issues:
<https://autobuilder.yocto.io/pub/non-release/patchmetrics/> CVE metrics 

 

YP 4.2 Milestone Dates:

*       YP 4.2 M1 is released
*       YP 4.2 M2 build date 2023/01/23
*       YP 4.2 M2 Release date 2023/02/03
*       YP 4.2 M3 build date 2023/02/20
*       YP 4.2 M3 Release date 2023/03/03
*       YP 4.2 M4 build date 2023/04/03
*       YP 4.2 M4 Release date 2023/04/28

 

Upcoming dot releases:

*       YP 4.0.6 is released
*       YP 4.1.2 build date 2023/01/09
*       YP 4.1.2 Release date 2023/01/20
*       YP 3.1.22 build date 2023/01/16
*       YP 3.1.22 Release date 2023/01/27
*       YP 4.0.7 build date 2023/01/30
*       YP 4.0.7 Release date 2023/02/10
*       YP 3.1.23 build date 2023/02/13
*       YP 3.1.23 Release date 2023/02/24
*       YP 4.0.8 build date 2023/02/27
*       YP 4.0.8 Release date 2023/03/10
*       YP 4.1.3 build date 2023/03/06
*       YP 4.1.3 Release date 2023/03/17
*       YP 3.1.24 build date 2023/03/20
*       YP 3.1.24 Release date 2023/03/31
*       YP 4.0.9 build date 2023/04/10
*       YP 4.0.9 Release date 2023/04/21
*       YP 4.1.4 build date 2023/05/01
*       YP 4.1.4 Release date 2023/05/13
*       YP 3.1.25 build date 2023/05/08
*       YP 3.1.25 Release date 2023/05/19
*       YP 4.0.10 build date 2023/05/15
*       YP 4.0.10 Release date 2023/05/26

 

Tracking Metrics:

*       WDD 2457 (last week 2452) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
*       OE-Core/Poky Patch Metrics

*       Total patches found: 1189 (last week 1188)
*       Patches in the Pending State: 282 (24%) [last week 282 (24%)]

*        <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
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>
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:
<https://wiki.yoctoproject.org/wiki/Weekly_Status>
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:              [email protected]
<mailto:[email protected]> 

 

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

Reply via email to