From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW11`21
Date: Tue, 23 Mar 2021 07:43:27 -0700 [thread overview]
Message-ID: <1bc401d71ff2$e307b9c0$a9172d40$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4725 bytes --]
Current Dev Position: YP 3.3 M4 (Feature Freeze)
Next Deadline: 5th April 2021 YP 3.3 M4 build
Next Team Meetings:
* Bug Triage meeting Thursday Mar. 25th 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. 23rd 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 rc1 had an issue with the beaglebone reference platform.
As such, we plan to build an rc2 when this has been fixed.
* The release series name for core has been bumped to "hardknott" and
the previous one, "gatesgarth" has now been removed. We do this so that
layers being actively maintained can be clearly identified compared to those
which are not. Layers will need to be updated to show compatibility with the
3.3 core.
* We've taken a number of version upgrades and other changes as the
benefits to taking them seem to outweigh the potential risk.
* There is a pending change to remove 'stale' sstate task output
before the main build starts in master-next. This has been testing for a
while with no reports of issues and seems to perform well so will likely be
included in M3 rc2.
* "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
We are working to identify the load pattern on the infrastructure that seems
to trigger these.
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 will go back to QA for rc2 soon.
* 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/22
* YP 3.2.3 release date 2021/04/02
* 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 2748 (last week 2759) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1309 (last week 1319)
* Patches in the Pending State: 492 (38%) [last week 489 (37%)]
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: 42673 bytes --]
next reply other threads:[~2021-03-23 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 14:43 Stephen Jolley [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-16 14:48 Yocto Project Status WW11`21 Stephen Jolley
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='1bc401d71ff2$e307b9c0$a9172d40$@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox