From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW31'20
Date: Tue, 4 Aug 2020 07:46:39 -0700 [thread overview]
Message-ID: <028901d66a6e$0fee7180$2fcb5480$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3637 bytes --]
Current Dev Position: YP 3.2 M3
Next Deadline: YP 3.2 M3 build date 2020/8/31
Next Team Meetings:
* Bug Triage meeting Thursday Aug. 6th at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
* Monthly Project Meeting Tuesday Aug. 4th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Weekly Engineering Sync Tuesday Aug. 11th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Twitch - See https://www.twitch.tv/theyoctojester
Key Status/Updates:
* 3.1.2 was released
* 3.2 M2 is currently under QA
* We continue to see qemumips systemd (poky-altcfg) image testing
failures for unknown reasons although it does seem linked to the poor
performance of mips emulation under qemu.
* The project has published a plan related to use of inclusive
language within the project (covering Yocto Project and OpenEmbedded). This
was posted to the openembedded-architecture list:
<https://lists.openembedded.org/g/openembedded-architecture/topic/inclusive_
language_summary/75821819>
https://lists.openembedded.org/g/openembedded-architecture/topic/inclusive_l
anguage_summary/75821819
* Documentation covering the potential "future directions" for Yocto
Project has been published:
<https://lists.openembedded.org/g/openembedded-architecture/topic/yocto_proj
ect_future/75845140>
https://lists.openembedded.org/g/openembedded-architecture/topic/yocto_proje
ct_future/75845140
* You can see the rest of 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 with any of these would be much appreciated.
* One way to help the project is to help us with bugs that are
currently unassigned but ideally needed during YP 3.2. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhan
cements.2FBugs
* Help with any of the recent failed AUH recipe upgrades would also be
appreciated.
YP 3.2 Milestone Dates:
* YP 3.2 M2 build is in QA
* YP 3.2 M2 Release date 2020/8/7
* YP 3.2 M3 build date 2020/8/31
* YP 3.2 M3 Release date 2020/9/11
* YP 3.2 M4 build date 2020/10/5
* YP 3.2 M4 Release date 2020/10/30
Planned upcoming dot releases:
* YP 3.0.4 build date 2020/8/10
* YP 3.0.4 release date 2020/8/21
* YP 3.1.2 is released
* YP 3.1.3 build date 2020/9/14
* YP 3.1.3 release date 2020/9/25
Tracking Metrics:
* WDD 2402 (last week 2415) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1271 (last week 1281)
* Patches in the Pending State: 495 (39%) [last week 498 (39%)]
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: 39747 bytes --]
reply other threads:[~2020-08-04 14: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='028901d66a6e$0fee7180$2fcb5480$@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