From: <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW09'19
Date: Tue, 26 Feb 2019 07:58:00 -0800 [thread overview]
Message-ID: <010401d4cdec$0cbb3b80$2631b280$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3894 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: Ross -> Chen on Mar. 1, 2019
* SWAT team rotation: Chen -> Armin on Mar. 8, 2019
* <https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team>
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
* We have now passed the feature freeze point for 2.7
* YP 2.7 M2 rc2 is out of QA and being readied for release. See:
<https://wiki.yoctoproject.org/wiki/WW07_-_2019-02-14_-_Full_Test_Cycle_2.7_
M2_RC2>
https://wiki.yoctoproject.org/wiki/WW07_-_2019-02-14_-_Full_Test_Cycle_2.7_M
2_RC2 and
<https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status#Milestone_2_-_
Target_Feb._1.2C_2019>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status#Milestone_2_-_T
arget_Feb._1.2C_2019
* We now have resulttool, buildhistory and build-performance all
working with the autobuilder and will be using this as the primary QA
mechanism going forward. More details can be found here:
<http://lists.openembedded.org/pipermail/openembedded-architecture/2019-Febr
uary/001591.html>
http://lists.openembedded.org/pipermail/openembedded-architecture/2019-Febru
ary/001591.html
* There were some serious usability issues found with multiconfig,
those have been fixed in master and thud.
* Various recipe upgrades made it in, thanks to all who contributed.
Several recipes also converted to meson including glib-2.0 and gdk-pixbuf.
* We now need to build M3 as we're past feature freeze point for 2.7.
Right now we're aware of the following things which ideally need to be
resolved first:
* Bug 13178 "X server and matchbox desktop don't start up properly on
beaglebone" needs to be fixed
* Find the framebuffer problem with qemuarmv7 and switch to that
* Several ptest issues would be addressed (missing openssl tests, 3
timeouts)
* Arm build host issues identified and resolved
* It's unlikely we'll switch to virtgl by default for 2.7 due to lack
of testing from the community although the base patches for this have
merged.
Planned Releases for YP 2.7:
* YP 2.7 M2 rc2 is out of QA.
* YP 2.7 M2 Release Target was Feb. 1, 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 2415 (last week 2392) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1516 (last week 1527)
* Patches in the Pending State: 660 (44%) [last week 663 (43%)]
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 Program Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 38557 bytes --]
reply other threads:[~2019-02-26 15:58 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='010401d4cdec$0cbb3b80$2631b280$@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