From: <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW07'19
Date: Tue, 12 Feb 2019 08:10:21 -0800 [thread overview]
Message-ID: <03b301d4c2ed$7497f360$5dc7da20$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4419 bytes --]
Current Dev Position: YP 2.7 M3
Next Deadline: YP 2.7 M3 Cutoff is Feb. 25, 2019
SWAT Team Rotation:
* SWAT lead is currently: Paul
* SWAT team rotation: Paul -> Ross on Feb. 15, 2019
* SWAT team rotation: Ross -> Amanda on Feb. 22, 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 M2 rc1 had major problems in perl as fallout from the perl
upgrade and switch to perl-cross. We've therefore built an rc2 based on a
more recent master.
* The python upgrade to 3.7 merged, thanks to AlexK for his hard work
on this. It means all of the major components in OE-Core are finally up to
date (many minor versions are still adrift).
* Major util-linux changes have just merged which should hopefully
allow easier long term maintenance of this recipe (all binaries now have
their own package, this recipe kept being split up)
* Build performance tests on the autobuilder have been improved and
builds now have automated result comparisons, e.g.:
<https://autobuilder.yocto.io/pub/non-release/20190212-7/testresults/buildpe
rf-ubuntu1604/perf-ubuntu1604_master_20190212045844_be52da1.html>
https://autobuilder.yocto.io/pub/non-release/20190212-7/testresults/buildper
f-ubuntu1604/perf-ubuntu1604_master_20190212045844_be52da1.html (from
<https://autobuilder.yoctoproject.org/typhoon/#/builders/92/builds/101>
https://autobuilder.yoctoproject.org/typhoon/#/builders/92/builds/101)
(Thanks to Markus for a lot of the underlying code/work)
* Build performance can now compare master to master-next test builds
* We continue to need help with ptest, both on the tests themselves
and on the results reporting. The intent is to have something similar to the
build performance pieces above.
* The recipe reporting system integration with the layer index is
available at: <https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/>
https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the
historical data has now been imported.
* The project is considering moving its mailing list hosting to
groups.io, if anyone has any experience of that, positive or negative please
let Michael, Nico and Richard know. Note that google has made further
significant changes to its mail processing at the detriment to mailing
lists:
<https://lists.freedesktop.org/archives/freedesktop/2019-February/000396.htm
l>
https://lists.freedesktop.org/archives/freedesktop/2019-February/000396.html
* If anyone has feedback about the maintainers/recipe upgrade
processes or how to attract new recipe maintainers, please talk to Richard
Purdie / Ross Burton
Planned Releases for YP 2.7:
* YP 2.7 M2 is being rebuilt and will go back to QA for rc2.
* YP 2.7 M2 Release Target is 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 2353 (last week 2356) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1527 (last week 1572
* Patches in the Pending State: 663 (43%) [last week 678 (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 Project Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 36388 bytes --]
next reply other threads:[~2019-02-12 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 16:10 sjolley.yp.pm [this message]
2019-02-12 17:22 ` Yocto Project Status WW07'19 Alexander Kanavin
2019-02-13 1:57 ` Paul Eggleton
2019-02-14 9:13 ` Michael Halstead
2019-02-14 10:27 ` Alexander Kanavin
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='03b301d4c2ed$7497f360$5dc7da20$@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