From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW10`21
Date: Tue, 9 Mar 2021 07:45:53 -0800 [thread overview]
Message-ID: <1c9a01d714fb$49f9bf50$dded3df0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5101 bytes --]
Current Dev Position: YP 3.3 Feature Freeze
Next Deadline: 1st March 2021 YP 3.3 M3 build
Next Team Meetings:
* Bug Triage meeting Thursday Mar. 11th at 7:30am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Monthly Project Meeting Tuesday Apr. 6th at 8am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
* Weekly Engineering Sync Tuesday Mar. 9th at 8am 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
Key Status/Updates:
* YP 3.3 M3 is due to build soon, we are now at feature freeze
* M3 has not been built yet whilst the status of various pending
patches was ascertained and several bugs investigated. A key runqueue bug in
bitbake was finally identified and resolved, other seeming state manifest
issues were traced to a bad patch. There is a performance regression which
still needs debugging and fixing. We also need to get a better understanding
of autobuilder load issues triggering intermittent failures although that
may be deferred to M4.
* It looks like the rust addition patches will be deferred to 3.4, as
will the PR server changes.
* Reproducibility is trending well for this release at 99.83% with a
remaining intermittent issue in ltp due to be fixed imminently. Meson and
ruby have intermittent issues, ovmf has a hardcoded path and much progress
has been made in resolving the perf issues so hopefully that will be fixed
soon. The only other issue is Go Language related.
<https://www.yoctoproject.org/reproducible-build-results/>
https://www.yoctoproject.org/reproducible-build-results/
We had a mention in Reproducible Builds newsletter:
<https://reproducible-builds.org/reports/2021-02/>
https://reproducible-builds.org/reports/2021-02/
* "Pending" state patch review is still needed, we have some really
old stale ones which really need decisions to be made about their future. It
would help a lot if recipe maintainers could review recipe patchsets and
upstream them or remove them if they are no longer relevant.
* Intermittent autobuilder issues continue to occur and are now at a
record high level. 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
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 3.3. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_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.
YP 3.3 Milestone Dates:
* YP 3.3 M3 build date 2021/03/01
* YP 3.3 M3 Release date 2021/03/12
* YP 3.3 M4 build date 2021/04/05
* YP 3.3 M4 Release date 2021/04/30
Planned upcoming dot releases:
* YP 3.2.3 build date 2021/03/15
* YP 3.2.3 release date 2021/03/26
* YP 3.1.7 build date 2021/03/29
* YP 3.1.7 release date 2021/04/09
* YP 3.2.4 build date 2021/05/3
* YP 3.2.4 release date 2021/05/14
* YP 3.1.8 build date 2021/05/17
* YP 3.1.8 release date 2021/05/28
Tracking Metrics:
* WDD 2709 (last week 2647) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1281 (last week 1280)
* Patches in the Pending State: 489 (38%) [last week 484 (38%)]
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: 55787 bytes --]
reply other threads:[~2021-03-09 15:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='1c9a01d714fb$49f9bf50$dded3df0$@gmail.com' \
--to=sjolley.yp.pm@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@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.