All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jolley, Stephen K" <stephen.k.jolley@intel.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW21’18
Date: Mon, 21 May 2018 15:18:25 +0000	[thread overview]
Message-ID: <9ADD3FDE8B189B4AA2F8A3C711F8155EC730CA94@fmsmsx111.amr.corp.intel.com> (raw)

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

Current Dev Position: YP 2.6 M1 is accepting patches.

Next Deadline: YP 2.6 M1 release is June 11, 2018


SWAT Team Rotation:

·         SWAT lead is currently: Ross

·         SWAT team rotation: Ross -> Paul on May 25, 2018

·         SWAT team rotation: Paul -> Tracy on June 1, 2018

·         https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

·         We thought 2.4.3 had built and gone into QA however it seems something wasn’t configured correctly and this didn’t happen. We’ll requeue it again today.

·         There was a second 2.6 planning technical call on 15th where some further topics for 2.6 were discussed and some people/companies showed interest in those areas.

·         The next discussion on 2.6 planning will happen on June 5, 2018 at 8am PDT.

·         There were blocking issues with the new buildbot/autobuilder codebase which were preventing feature parity between the old and new codebases but after discussion with upstream we now have a plan on how to move forward. This unblocks progress on the new infrastructure.


Planned Releases for YP 2.6:

·         YP 2.6 M1 Build Target is June 11, 2018

·         YP 2.6 M1 Release Target is June 22, 2018

·         YP 2.6 M2 Build Target is July 16, 2018

·         YP 2.6 M2 Release Target is July 27, 2018

·         YP 2.6 M3 Build Target is Aug. 27, 2018

·         YP 2.6 M3 Release Target is Sept. 7, 2018

·         YP 2.6 M4 Build Target is Oct. 1, 2018

·         YP 2.6 M4 Release Target is Oct. 26, 2018


Planned upcoming dot releases:

·         YP 2.3.4 (Pyro) will be built this week

·         YP 2.4.3 (Rocko) is planned for after 2.3.4

·         YP 2.2.4 (Morty) is planned for after 2.4.3


Tracking Metrics:

·         WDD 2510 (last week 2515) (https://wiki.yoctoproject.org/charts/combo.html)

·         Patches

o    Total patches found: 1599 (last week 1591)

o    Percentage of patches in the Pending State: 47% (last week 47%)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.6_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.6_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.6_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: 38946 bytes --]

                 reply	other threads:[~2018-05-21 15:18 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=9ADD3FDE8B189B4AA2F8A3C711F8155EC730CA94@fmsmsx111.amr.corp.intel.com \
    --to=stephen.k.jolley@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.