Openembedded Core Discussions
 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 WW15'20
Date: Tue, 21 Apr 2020 07:41:18 -0700	[thread overview]
Message-ID: <128801d617ea$eb67c1c0$c2374540$@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3420 bytes --]

Current Dev Position: YP 3.1 Being released

Next Deadline: YP 3.1 release date  2020/4/24

 

Next Team Meetings:

*	Bug Triage meeting Thursday Apr. 23rd 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. 21st  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 will be released imminently
*	We're pleased to be able to announce that the stable maintainer for
the 3.1 LTS release will be Steve Sakoman
*	YP 3.1 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/
*	The 3.2 planning document where we've been discussing potential 3.2
developments is available at:
<https://docs.google.com/document/d/100bTV-etO0joh6rAkcr7smlZ9iuENG_8BtaXs_v
b54c/edit?usp=sharing>
https://docs.google.com/document/d/100bTV-etO0joh6rAkcr7smlZ9iuENG_8BtaXs_vb
54c/edit?usp=sharing
*	Master branch development will open up later this week, there are
already some patches queued and tested in master-next
*	There is discussion on the openembedded-architecture list about a
particularly troublesome multilib issue which doesn't appear to have any
good resolution at present.
*	We are aware of some issues with bug trend metrics this week due to
server transitions and are working to resolve those.

 

YP 3.1 Dates:

*	YP 3.1 In review for release
*	YP 3.1 Release date 2020/4/24

 

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: 1364 (last week 1364)
*	Patches in the Pending State: 538 (39%) [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: 40928 bytes --]

             reply	other threads:[~2020-04-21 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 14:41 Stephen Jolley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-14 14:56 Yocto Project Status WW15'20 Stephen Jolley

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='128801d617ea$eb67c1c0$c2374540$@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