From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW17'20
Date: Tue, 28 Apr 2020 07:45:37 -0700 [thread overview]
Message-ID: <114201d61d6b$aea407e0$0bec17a0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3444 bytes --]
Current Dev Position: YP 3.2 M1
Next Deadline: YP 3.2 M1 build date 2020/6/16
Next Team Meetings:
* Bug Triage meeting Thursday Apr. 30th at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
* Monthly Project Meeting Tuesday May 5th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Weekly Engineering Sync Tuesday Apr. 28th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
* Twitch - See http://www.twitch.tv/letoatreidesthe2nd
Key Status/Updates:
* YP 3.1 was released, thanks to everyone who contributed!
* The stable maintainer for the 3.1 LTS release is Steve Sakoman
* YP 3.1 (dunfell) 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/
* Patches have started merging again into master. We've already had
some challenging issues to debug with them on the autobuilder where the root
cause turned out to be an underlying QA test code issue exposed by test
ordering issues.
* Master branch development will open up later this week, there are
already some patches queued and tested in master-next
* The multilib discussion on the openembedded-architecture list has
continued with the potential of new bitbake support to better enable class
extensions (which enable native and nativesdk variants as well as multilib).
* We've identified some issues with the new
buildtools-extended-tarball so we'll be making a new version of that and
porting fixes to the stable branch.
* We are aware of some issues with bug trend metrics this week due to
server transitions and are working to resolve those.
YP 3.2 Milestone Dates:
* YP 3.2 M1 build date 2020/6/16
* YP 3.2 M1 Release date 2020/6/26
* YP 3.2 M2 build date 2020/7/27
* YP 3.2 M2 Release date 2020/8/7
* YP 3.2 M3 build date 2020/8/31
* YP 3.2 M3 Release date 2020/9/11
* YP 3.2 M4 build date 2020/10/5
* YP 3.2 M4 Release date 2020/10/30
Planned upcoming dot releases:
* YP 3.0.3 build date 2020/5/4
* YP 3.0.3 release date 2020/5/15
* YP 2.7.4 build date 2020/5/18
* YP 2.7.4 release date 2020/5/29
* YP 3.1.1 build date 2020/6/29
* YP 3.1.1 release date 2020/7/10
* YP 3.0.4 build date 2020/8/10
* YP 3.0.4 release date 2020/8/21
* YP 3.1.2 build date 2020/9/14
* YP 3.1.2 release date 2020/9/25
Tracking Metrics:
* WDD 2577 (last week 2577) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* Poky Patch Metrics
* Total patches found: 1367 (last week 1364)
* Patches in the Pending State: 540 (40%) [last week 538 (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: 36871 bytes --]
reply other threads:[~2020-04-28 14:45 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='114201d61d6b$aea407e0$0bec17a0$@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