public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW18'20
Date: Tue, 5 May 2020 07:49:01 -0700	[thread overview]
Message-ID: <306d01d622ec$516fb570$f44f2050$@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3264 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 May 7th 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 May 12th  at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Twitch -  See http://www.twitch.tv/letoatreidesthe2nd

 

Key Status/Updates:

*	We are now merging patches into master, debugging some of the issues
has proven problematic but we're making good progress on various deferred
upgrades.
*	In particular there was a further problem with
buildtools-extended-tarball which ended up 'corrupting' sstate by
over-optimising binaries so they wouldn't run on older CPUs. Fixes for this
have merged and we'll need to release a new buildtools tarball.
*	The 3.1 stable branch has started taking its first rounds of
patches, help with review of these would be much appreciated.
*	A 3.0 stable build is due as soon as the current patches in review
are sorted out.
*	The multilib issue mentioned in previous status reports and on the
architecture list is proving tricky, do we make the invasive changes in
master-next for master now they appear to work? Backport to dunfell? Or try
and come up with a more invasive core bitbake change?
*	We are aware of some issues with bug trend metrics 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: 1353 (last week 1367)
*	Patches in the Pending State: 536 (40%) [last week 540 (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 Program Manager

*    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com> 

 


[-- Attachment #2: Type: text/html, Size: 34345 bytes --]

                 reply	other threads:[~2020-05-05 14: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='306d01d622ec$516fb570$f44f2050$@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