From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW12'20
Date: Tue, 24 Mar 2020 07:53:54 -0700 [thread overview]
Message-ID: <0ec301d601ec$0a1b01a0$1e5104e0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2519 bytes --]
Current Dev Position: YP 3.1 M4 - Stabilization
Next Deadline: YP 3.1 M4 build date 3/30/2020
Next Team Meetings:
* Bug Triage meeting Thursday Mar. 26th at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
* Monthly Project Meeting Tuesday Apr. 7th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Weekly Engineering Sync Tuesday Mar. 24th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Twitch - See http://www.twitch.tv/letoatreidesthe2nd
Key Status/Updates:
* M3 is through QA and due to be released.
* The first M4 rc candidate is due to be built on Monday.
* YP 3.1 has been announced as an LTS release:
<https://www.yoctoproject.org/yocto-project-long-term-support-announced/>
https://www.yoctoproject.org/yocto-project-long-term-support-announced/
* We've uncovered significant issues with the datastore connector
approach in tinfoil. There is a proposed fix which effectively rewrites it
which is not something undertaken lightly at this point in release but
reluctantly, is probably necessary.
* The focus is now on stabilizing and bug fixing for the final release
YP 3.1 Milestone Dates:
* YP 3.1 M3 being reviewed for release
* 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.3 build date 5/4/2020
* YP 3.0.3 release date 5/15/2020
* YP 2.7.4 build date 5/18/2020
* YP 2.7.4 release date 5/29/2020
Tracking Metrics:
* WDD 2681 (last week 2698) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1350 (last week 1351)
* Patches in the Pending State: 535 (40%) [last week 534 (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 Program Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 32807 bytes --]
reply other threads:[~2020-03-24 14:53 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='0ec301d601ec$0a1b01a0$1e5104e0$@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