From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>,
<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status 29 November 2022 (WW48)
Date: Tue, 29 Nov 2022 08:44:56 -0700 [thread overview]
Message-ID: <0b6801d90409$885d6860$99183920$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5240 bytes --]
Current Dev Position: YP 4.2 M1
Next Deadline: 5th December 2022 YP 4.2 Build
Next Team Meetings:
* Bug Triage meeting Thursday December 8th 7:30 am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Weekly Project Engineering Sync Tuesday December 6th 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 3.1.21 has passed QA and will be released.
* It is Yocto Project Summit and OEDVM this week so many people will
be attending those events. Thanks to everyone participating or helping
enable to happen.
* There is some discussion on the architecture list about some changes
to bitbake including adding new API to handle python libraries.
* In particular we have a dilemma on whether to accept a parsing
overhead for improved variable flag handling (export, unexport, network
flags) or for better cache data to improve hash debugging.
* Unfs was upgraded and automated testing enabled. Being able to mount
a local filesystem into qemu images or real hardware as the rootfs over NFS
can be a useful way to develop or debug issues so it is timely to remind
people this is possible. No special user permissions are needed as it is
handled in userspace.
* We'd welcome a proposal/series on how to move forward with the Y2038
work for 32 bit platforms.
* We have a growing number of bugs in bugzilla, any help with them is
appreciated.
Ways to contribute:
* 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 build date 2022/12/05
* YP 4.2 M1 Release date 2022/12/16
* 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 3.1.21 is ready for release
* YP 4.0.6 build date 2022/12/12
* YP 4.0.6 Release date 2022/12/23
* 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 2446 (last week 2436) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
* Total patches found: 1175 (last week 1178)
* Patches in the Pending State: 288 (25%) [last week 289 (25%)]
* <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: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 45364 bytes --]
next reply other threads:[~2022-11-29 15:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 15:44 sjolley.yp.pm [this message]
2022-11-30 8:07 ` Y2038 proposal Alexander Kanavin
2022-11-30 8:28 ` [yocto] " Lukasz Majewski
2022-11-30 9:07 ` Alexander Kanavin
2022-11-30 9:40 ` Lukasz Majewski
2022-11-30 9:48 ` Alexander Kanavin
2022-11-30 21:14 ` Alexander Kanavin
2022-12-01 8:28 ` Lukasz Majewski
2022-11-30 10:52 ` Stephen John Smoogen
2022-11-30 11:04 ` Lukasz Majewski
2022-11-30 12:09 ` Alexander Kanavin
2022-11-30 11:02 ` Alexandre Belloni
2022-11-30 11:40 ` [OE-core] " Richard Purdie
2022-11-30 12:07 ` Alexander Kanavin
2022-11-30 12:09 ` Lukasz Majewski
2022-11-30 12:11 ` Richard Purdie
2022-11-30 13:15 ` [Openembedded-architecture] " Richard Purdie
2022-11-30 13:36 ` [OE-core] " Lukasz Majewski
2022-11-30 14:20 ` Richard Purdie
2022-11-30 16:46 ` [yocto] " Ross Burton
2022-11-30 16:56 ` Alexandre Belloni
2022-11-30 16:59 ` Richard Purdie
2022-12-05 10:00 ` Ola x Nilsson
2022-12-05 11:04 ` Richard Purdie
2022-12-05 11:05 ` Ola x Nilsson
2022-12-01 10:27 ` Alexander Kanavin
2022-12-01 10:36 ` Richard Purdie
2022-11-30 16:38 ` Khem Raj
2022-12-02 8:54 ` [OE-core] " Matt Johnston
2022-12-05 23:24 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='0b6801d90409$885d6860$99183920$@gmail.com' \
--to=sjolley.yp.pm@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.