From: <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Cc: Lieu.Ta@windriver.com
Subject: Yocto Project Status WW49'19
Date: Tue, 3 Dec 2019 07:50:56 -0800 [thread overview]
Message-ID: <07da01d5a9f1$7390ce60$5ab26b20$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3547 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 Dec. 10th 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 3.0.1 is out of QA with good test results so should be released
soon.
* We have set a deadline of Monday 9th December for removing python2
support from OE-Core, a separate email was sent out about this. The patches
to do this are in master-next and they remove python and python2 from
HOSTTOOLS.
* Reproducible builds are now enabled by default in poky, we should
also consider this for the default in OE-Core.
* Hash equivalence continues to undergo testing and further work.
* We're likely to build M1 after the python 2 removal is merged next
week, also giving time for the hash equivalence work to move forward
further.
* 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 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 out of QA and should be released soon.
* 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 2620 (last week 2578) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1444 (last week 1450)
* Patches in the Pending State: 571 (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: 24321 bytes --]
reply other threads:[~2019-12-03 15:50 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='07da01d5a9f1$7390ce60$5ab26b20$@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox