From: <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Cc: Lieu.Ta@windriver.com
Subject: Yocto Project Status WW50'19
Date: Tue, 10 Dec 2019 07:40:16 -0800 [thread overview]
Message-ID: <049a01d5af70$1f5fd5f0$5e1f81d0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3512 bytes --]
Current Dev Position: YP 3.1 M1
Next Deadline: YP 3.1 M1 build Dec. 2, 2019
Next Team Meetings:
* Bug Triage meeting Thursday Dec. 12th at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
* Monthly Project Meeting Tuesday Jan. 7th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Weekly Engineering Sync Tuesday Dec. 10th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Twitch - Next event is Tuesday Dec. 17th at 8am PDT (
<https://www.twitch.tv/yocto_project> https://www.twitch.tv/yocto_project)
Key Status/Updates:
* YP 3.0.1 was released.
* Python 2.x has been removed from HOSTTOOLS so OE-Core is python2 use
free.
* Hash Equivalency has been enabled by default for poky using a local
server.
* YP 3.1 M1 was due to be built but issues have been encountered in
the release builds, both with previously unseen hash equivalence issue and a
ptest performance regression on the autobuilders. Both issues are being
worked on but are further delaying a successful M1 build.
* Intermittent build failures continue to hamper builds, particularly
combined with the above issues and as few people are available to attempt to
debug and resolve them.
* Patch review and testing has run into new issues with a number of
regressions from upgrades causing instability. Most of these were isolated
pre-merge but not all.
* The TSC is working on LTS plans, productive discussions have been
had and a new policy on handling this and stable releases should be
available in the coming weeks.
* We are continuing to collect ideas for YP 3.1 in this document:
<https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yj
nABc/edit?usp=sharing>
https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjn
ABc/edit?usp=sharing
* If anyone has any status items for the project they'd like to add to
the weekly reports, please email Richard and Stephen.
YP 3.1 Milestone Dates:
* YP 3.1 M1 build date 12/2/2019
* YP 3.1 M1 release date 12/13/2019
* YP 3.1 M2 build date 1/20/2020
* YP 3.1 M2 release date 1/31/2020
* YP 3.1 M3 build date 2/24/2020
* YP 3.1 M3 release date 3/6/2020
* YP 3.1 M4 build date 3/30/2020
* YP 3.1 M4 release date 4/24/2020
Planned upcoming dot releases:
* YP 3.0.1 is released.
* YP 2.7.3 build date 2/10/20
* YP 2.7.3 release date 2/21/20
* YP 3.0.2 build date 2/3/20
* YP 3.0.2 release date 2/14/20
Tracking Metrics:
* WDD 2698 (last week 2620) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1410 (last week 1444)
* Patches in the Pending State: 564 (40%) [last week 571 (40%)]
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 Project Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 34651 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Cc: <Lieu.Ta@windriver.com>, <sjolley.yp.pm@gmail.com>
Subject: Yocto Project Status WW50'19
Date: Tue, 10 Dec 2019 07:40:16 -0800 [thread overview]
Message-ID: <049a01d5af70$1f5fd5f0$5e1f81d0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3512 bytes --]
Current Dev Position: YP 3.1 M1
Next Deadline: YP 3.1 M1 build Dec. 2, 2019
Next Team Meetings:
* Bug Triage meeting Thursday Dec. 12th at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
* Monthly Project Meeting Tuesday Jan. 7th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Weekly Engineering Sync Tuesday Dec. 10th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Twitch - Next event is Tuesday Dec. 17th at 8am PDT (
<https://www.twitch.tv/yocto_project> https://www.twitch.tv/yocto_project)
Key Status/Updates:
* YP 3.0.1 was released.
* Python 2.x has been removed from HOSTTOOLS so OE-Core is python2 use
free.
* Hash Equivalency has been enabled by default for poky using a local
server.
* YP 3.1 M1 was due to be built but issues have been encountered in
the release builds, both with previously unseen hash equivalence issue and a
ptest performance regression on the autobuilders. Both issues are being
worked on but are further delaying a successful M1 build.
* Intermittent build failures continue to hamper builds, particularly
combined with the above issues and as few people are available to attempt to
debug and resolve them.
* Patch review and testing has run into new issues with a number of
regressions from upgrades causing instability. Most of these were isolated
pre-merge but not all.
* The TSC is working on LTS plans, productive discussions have been
had and a new policy on handling this and stable releases should be
available in the coming weeks.
* We are continuing to collect ideas for YP 3.1 in this document:
<https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yj
nABc/edit?usp=sharing>
https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjn
ABc/edit?usp=sharing
* If anyone has any status items for the project they'd like to add to
the weekly reports, please email Richard and Stephen.
YP 3.1 Milestone Dates:
* YP 3.1 M1 build date 12/2/2019
* YP 3.1 M1 release date 12/13/2019
* YP 3.1 M2 build date 1/20/2020
* YP 3.1 M2 release date 1/31/2020
* YP 3.1 M3 build date 2/24/2020
* YP 3.1 M3 release date 3/6/2020
* YP 3.1 M4 build date 3/30/2020
* YP 3.1 M4 release date 4/24/2020
Planned upcoming dot releases:
* YP 3.0.1 is released.
* YP 2.7.3 build date 2/10/20
* YP 2.7.3 release date 2/21/20
* YP 3.0.2 build date 2/3/20
* YP 3.0.2 release date 2/14/20
Tracking Metrics:
* WDD 2698 (last week 2620) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1410 (last week 1444)
* Patches in the Pending State: 564 (40%) [last week 571 (40%)]
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 Project Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 34651 bytes --]
next reply other threads:[~2019-12-10 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 15:40 sjolley.yp.pm [this message]
2019-12-10 15:40 ` Yocto Project Status WW50'19 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='049a01d5af70$1f5fd5f0$5e1f81d0$@gmail.com' \
--to=sjolley.yp.pm@gmail.com \
--cc=Lieu.Ta@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.