From: <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW46'19
Date: Tue, 12 Nov 2019 07:47:13 -0800 [thread overview]
Message-ID: <014c01d59970$73f28c40$5bd7a4c0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3634 bytes --]
Current Dev Position: YP 3.1 M1
Next Deadline: YP 3.1 M1 build Dec. 2, 2019
SWAT Team Rotation:
* SWAT lead is currently: Anuj
* SWAT team rotation: Anuj -> Chen on Nov. 15, 2019
* SWAT team rotation: Chen > Paul on Nov. 22, 2019
* <https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team>
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Next Team Meetings:
* Bug Triage meeting Thursday Nov. 14th 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. 12th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Twitch - Next event is Tuesday Nov. 12th at 8am PDT (
<https://www.twitch.tv/yocto_project> https://www.twitch.tv/yocto_project)
Key Status/Updates:
* YP 2.7.2 is still undergoing QA
* There were some key fixes for pseudo related issues which mean it
continues to work with modern distros like Fedora 31.
* Patches have continued to merge and master is staying roughly
current with the pending patch queue but there continue to be recurring
build failures that are not being addressed.
* The YP TSC worked on and shared a proposal on how an LTS release
could work which is available at:
<https://docs.google.com/document/d/1AwAFDf52f_FoXksbHEVUMlu4hpcI0JMGVG-Kj_s
Ukyc/>
https://docs.google.com/document/d/1AwAFDf52f_FoXksbHEVUMlu4hpcI0JMGVG-Kj_sU
kyc/ . There has been much discussion about this, patience would be
appreciated as the TSC and governing board work through this to come up with
plans on how we proceed.
* 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.
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 3.0.1 has patches being queued in poky-contrib
* YP 2.7.2 (Warrior) is in QA.
Tracking Metrics:
* WDD 2508 (last week 2518) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1445 (last week 1446)
* 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: <mailto:sjolley.yp.pm@gmail.com>
sjolley.yp.pm@gmail.com
[-- Attachment #2: Type: text/html, Size: 26400 bytes --]
next reply other threads:[~2019-11-12 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 15:47 sjolley.yp.pm [this message]
2019-11-15 0:11 ` [yocto] Yocto Project Status WW46'19 akuster808
2019-11-15 0:11 ` akuster808
2019-11-15 0:17 ` [yocto] " Richard Purdie
2019-11-15 0:17 ` [OE-core] " Richard Purdie
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='014c01d59970$73f28c40$5bd7a4c0$@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 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.