From: <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW48'19
Date: Tue, 26 Nov 2019 07:47:14 -0800 [thread overview]
Message-ID: <05d101d5a470$c69d7d00$53d87700$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3955 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. 5th at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
* Monthly Project Meeting Tuesday Dec. 3rd at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Weekly Engineering Sync Tuesday Nov. 26th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Twitch - Next event is Tuesday Dec. 10th at 8am PDT (
<https://www.twitch.tv/yocto_project> https://www.twitch.tv/yocto_project)
Key Status/Updates:
* YP 2.7.2 should be released imminently.
* The reproducibility issues from last week have been addressed and we
are hoping to enable this by default soon, thanks to everyone who helped fix
issues.
* The news for hash equivalence is not so promising. Whilst a number
of bugs were fixed, we've found a major problem which explains some of the
failures we've seen and are currently working out how we may be able to
resolve that issue.
* 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.
* The focus on hash equivalence and reproducibility has slowed patch
merging in other areas. Patch testing has been problematic as there are a
lot of regressions being found in submitted patches which also slows down
the whole merging process.
* 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 next couple of 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
* Due to the number of key fixes being found we have delayed YP 3.0.1
being built slightly whilst we merge those fixes, it should build in the
next few days.
* If anyone has any status items for the project they'd like to add to
the weekly reports, please email Richard and Stephen.
Proposed YP 3.1 Milestone Dates:
* YP 3.1 M1 Proposed build date 12/2/2019
* YP 3.1 M1 Proposed release date 12/13/2019
* YP 3.1 M2 Proposed build date 1/20/2020
* YP 3.1 M2 Proposed release date 1/31/2020
* YP 3.1 M3 Proposed build date 2/24/2020
* YP 3.1 M3 Proposed release date 3/6/2020
* YP 3.1 M4 Proposed build date 3/30/2020
* YP 3.1 M4 Proposed release date 4/24/2020
Planned upcoming dot releases:
* YP 2.7.2 Should release this week.
* YP 3.0.1 Proposed build date 11/25/2019
* YP 3.0.1 Proposed release date 12/06/2019
* YP 2.7.3 Proposed build date 2/10/20
* YP 2.7.3 Proposed release date 2/21/20
* YP 3.0.2 Proposed build date 2/3/20
* YP 3.0.2 Proposed release date 2/14/20
Tracking Metrics:
* WDD 2578 (last week 2533) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1450 (last week 1461)
* Patches in the Pending State: 579 (40%) [last week 579 (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: 36936 bytes --]
reply other threads:[~2019-11-26 15:47 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='05d101d5a470$c69d7d00$53d87700$@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