From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW50'20
Date: Tue, 15 Dec 2020 07:49:30 -0800 [thread overview]
Message-ID: <116f01d6d2f9$e0798bc0$a16ca340$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4571 bytes --]
Current Dev Position: YP 3.3 M2 development
Next Deadline: 18th January 2021 YP 3.3 M2 build
Next Team Meetings:
* Bug Triage meeting Thursday Dec. 17th at 7:30am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Monthly Project Meeting Tuesday Jan. 5th at 8am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
* Weekly Engineering Sync Tuesday Dec. 15th at 8am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
* Twitch - See https://www.twitch.tv/theyoctojester
Key Status/Updates:
* YP 3.2.1 is due for imminent release
* YP 3.3 M1 has been through QA and currently under review from the
TSC
* Patches for 3.3 M2 are now being reviewed, tested and merged.
* The project's work on reproducibility was mentioned in their monthly
newsletter <https://reproducible-builds.org/reports/2020-11/>
https://reproducible-builds.org/reports/2020-11/
* CVE statistics continue to look worse for master after
'improvements' to the matching code, help in resolving these newly
highlighted issues would be much appreciated.
* Intermittent autobuilder issues continue to occur. You can see the
list of failures we're continuing to see by searching for the "AB-INT" tag
in bugzilla:
<https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT>
https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
* Given the vacation many people are taking at this time and the
expected ramp down in patch load and newsworthy items, we're not planning
another status report until 5th January. The project technical and triage
meetings will also ramp down for this period and resume in the first week of
January unless there is any pressing development that needs urgent
attention.
Ways to contribute:
* There are bugs identified as possible for newcomers to the project:
<https://wiki.yoctoproject.org/wiki/Newcomers>
https://wiki.yoctoproject.org/wiki/Newcomers
* There are bugs that are currently unassigned for YP 3.3. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enhan
cements.2FBugs
* We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:
<http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/mai
ntainers.inc>
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.
YP 3.3 Milestone Dates:
* YP 3.3 M1 is out of QA.
* YP 3.3 M2 build date 2021/01/18
* YP 3.3 M2 Release date 2021/01/29
* YP 3.3 M3 build date 2021/03/01
* YP 3.3 M3 Release date 2021/03/12
* YP 3.3 M4 build date 2021/04/05
* YP 3.3 M4 Release date 2021/04/30
Planned upcoming dot releases:
* YP 3.2.1 should release soon.
* YP 3.1.5 build date 2021/01/11
* YP 3.1.5 release date 2021/01/22
* YP 3.2.2 build date 2021/02/08
* YP 3.2.2 release date 2021/02/19
* YP 3.1.6 build date 2021/02/22
* YP 3.1.6 release date 2021/03/05
* YP 3.1.7 build date 2021/03/22
* YP 3.1.7 release date 2021/04/02
Tracking Metrics:
* WDD 2513 (last week 2547) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1300 (last week 1288)
* Patches in the Pending State: 504 (39%) [last week 496 (39%)]
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: 41270 bytes --]
reply other threads:[~2020-12-15 15:49 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='116f01d6d2f9$e0798bc0$a16ca340$@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