From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW45'20
Date: Tue, 10 Nov 2020 07:46:10 -0800 [thread overview]
Message-ID: <109901d6b778$9cf886e0$d6e994a0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5188 bytes --]
Current Dev Position: YP 3.3 M1 development
Next Deadline: 7th December 2020 YP 3.3 M1 build
Next Team Meetings:
* Bug Triage meeting Thursday Nov. 12th at 7:30am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Monthly Project Meeting Tuesday Dec. 1st 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 Nov. 10th 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 has been released
* Master has now opened up for 3.3 development. Unfortunately there
have been a lot of issues showing up with some of the more adventurous
patches being proposed, the issues are being worked through.
* 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
* A YP 3.3 planning document has been created for ideas about what may
happen in the YP 3.3 release (assuming there are people to work on the
items):
<https://docs.google.com/document/d/1IHiE0NU0XspDocgxZeLQ_W7o-yr0nVeBjbqImQU
tH5A/edit>
https://docs.google.com/document/d/1IHiE0NU0XspDocgxZeLQ_W7o-yr0nVeBjbqImQUt
H5A/edit Request edit/suggest access if you want to add to it.
* YP 3.3 dates for builds, milestones and release have been added
below.
* Anuj Mittal has kindly agreed to maintain the YP 3.2 series
(gatesgarth), thanks!
* The SWAT team has been re-established. A new mailing has been
created as <mailto:swat@lists.yoctoproject.org> swat@lists.yoctoproject.org
to support this and a number of member organisations have agreed to help
staff this team. We are in the process of getting the process running again
and in due course there will be the option of other community members being
able to help too. The tools and processes are under review to allow us to
optimise the process. Thanks to the members and everyone participating to
make this happen!
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.2 Milestone Dates:
* YP 3.2 M4 released
YP 3.3 Milestone Dates:
* YP 3.3 M1 build date 2020/12/07
* YP 3.3 M1 Release date 2020/12/18
* 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.1.4 build date 2020/11/2
* YP 3.1.4 release date 2020/11/13
* YP 3.2.1 build date 2020/11/16
* YP 3.2.1 release date 2020/12/4
* 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 2524 (last week 2492) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1268 (last week 1264)
* Patches in the Pending State: 495 (39%) [last week 495 (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: 55390 bytes --]
reply other threads:[~2020-11-10 15:46 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='109901d6b778$9cf886e0$d6e994a0$@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