From: <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW10'19
Date: Tue, 5 Mar 2019 07:48:20 -0800 [thread overview]
Message-ID: <01a501d4d36a$dc4bdb60$94e39220$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3081 bytes --]
Current Dev Position: YP 2.7 M3 (New feature Freeze has begun.)
Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019
SWAT Team Rotation:
* SWAT lead is currently: Ross
* SWAT team rotation: Chen -> Anuj on Mar. 8, 2019
* SWAT team rotation: Anuj -> Armin on Mar. 15, 2019
* <https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team>
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
* YP 2.7 M2 rc2 is being released today Mar. 5, 2019.
* YP 2.7 M3 has not yet been built but progress has been made in
resolving several issues:
* bug 13178 "X server and matchbox desktop don't start up properly on
beaglebone" was fixed
* multiconfig bugs have been fixed and a test case added
* qemu virgl code and selftests have been added (not enabled as
default)
* qemu native build was split into user and system components
* lttng-tools ptest timeout fixed
* systemd version upgrade
* ltp recipe version upgrade
* perl ptest regressions fixed
* The list of remaining potential items for M3 is:
* 5.0 linux kernel (and libc headers) (Bruce)
* qemuarm to v7 changes (Jon)
* Aarch64 build host support finalization (Jon)
* Busybox 'full' utility replacement (Tom)
* YP 2.5.3 is nearly ready for building however the autobuilder-helper
changes need to be resolved for the stable branches, as do the resulttool
changes in master to move to the new QA process.
Planned Releases for YP 2.7:
* YP 2.7 M2 Released Mar. 5, 2019
* YP 2.7 M3 Cutoff is Feb. 25, 2019
* YP 2.7 M3 Release Target is Mar. 8, 2019
* YP 2.7 M4 Cutoff is Apr. 1, 2019
* YP 2.7 M4 Release Target is Apr. 26, 2019
Planned upcoming dot releases:
* YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
* YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
* YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.
Tracking Metrics:
* WDD 2436 (last week 2415) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1502 (last week 1516)
* Patches in the Pending State: 658 (44%) [last week 660 (44%)]
Key Status Links for YP:
<https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status
<https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule
<https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features
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 Project Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 38709 bytes --]
reply other threads:[~2019-03-05 15:48 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='01a501d4d36a$dc4bdb60$94e39220$@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