From: akuster808 <akuster808@gmail.com>
To: "Jolley, Stephen K" <stephen.k.jolley@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] Yocto Project Status WW19’18
Date: Mon, 7 May 2018 16:46:45 -0700 [thread overview]
Message-ID: <f2ec37a9-e623-9b29-b571-e4c8594aa66e@gmail.com> (raw)
In-Reply-To: <9ADD3FDE8B189B4AA2F8A3C711F8155EC72F644A@fmsmsx111.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2920 bytes --]
On 05/07/2018 08:01 AM, Jolley, Stephen K wrote:
>
> Current Dev Position: YP 2.5 is in QA.
>
> Next Deadline: YP 2.5 M4 release is 4/27/18
>
>
>
> SWAT Team Rotation:
>
> · SWAT lead is currently: Stephano
>
I am covering this week for stephano.
- armin
>
> · SWAT team rotation: Stephano -> Maxin on May 11, 2018
>
> · SWAT team rotation: Maxin-> Armin on May 18, 2018
>
> · https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>
>
>
> Key Status/Updates:
>
> · 2.5 rc1 should be due from QA early this week. It is 96%
> complete. See: https://wiki.yoctoproject.org/wiki/2.5_QA_Status
>
> · The need for any rc2 is still to be determined when the
> report is complete.
>
> · The technical call on 1st May started discussions on 2.6
> planning. Some threads were started on the openembedded-architecture
> mailing list for some of the topics which need discussion. The email
> linked to below details the planning process we will be following
> along with some of the possible ideas for 2.6:
> http://lists.openembedded.org/pipermail/openembedded-core/2018-April/150040.html
>
> · A further 2.6 planning meeting will be scheduled at the same
> time as the original meeting on 15th May to continue the discussion
> (8am PST, 4pm GMT).
>
> · We have started merging patches into master again to clear
> some of the backlog, particularly the recipe upgrades. This improved
> the overall patch count in metrics below.
>
>
>
> Planned upcoming dot releases:
>
> · YP 2.3.4 (Pyro) will be built after 2.5
>
> · YP 2.2.4 (Morty) will be built after 2.5
>
> · YP 2.4.3 (Rocko) is planned for post YP 2.5
>
>
>
> Key YP 2.5 Dates are:
>
> · YP 2.5 M4 release of 4/27/18
>
>
>
> Tracking Metrics:
>
> · WDD 2550 (last week
> 2508)(https://wiki.yoctoproject.org/charts/combo.html)
>
> · Patches
>
> o Total patches found: 1590 (last week 1635)
>
> o Percentage of patches in the Pending State: 47% (last week 46%)
>
>
>
> Key Status Links for YP:
>
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features
>
>
>
> The Status reports are now stored on the wiki at:
> 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 Project Manager*
>
> *INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 *
>
> ( *Cell*: (208) 244-4460
>
> * *Email*: _stephen.k.jolley@intel.com_
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 31841 bytes --]
prev parent reply other threads:[~2018-05-07 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 15:01 Yocto Project Status WW19’18 Jolley, Stephen K
2018-05-07 23:46 ` akuster808 [this message]
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=f2ec37a9-e623-9b29-b571-e4c8594aa66e@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stephen.k.jolley@intel.com \
--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