All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster <akuster@mvista.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 Project Status WW40
Date: Fri, 02 Oct 2015 09:10:02 -0700	[thread overview]
Message-ID: <560EAC5A.4020204@mvista.com> (raw)
In-Reply-To: <9ADD3FDE8B189B4AA2F8A3C711F8155E5569E669@fmsmsx111.amr.corp.intel.com>

Stephen,

Isn't the next meeting next Tuesday? Will there be a meeting since ELCE
is in full swing next week?

- armin

On 10/02/2015 08:26 AM, Jolley, Stephen K wrote:
> Current Dev Position: YP 2.0 Final (rc1 build in QA)
> Next Deadline: YP 2.0 Final Release Target: Before Oct. 30, 2015
> 
> SWAT team rotation: Ross -> Cristian
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
> 
> Key Status/Updates:
> 
>   *   Two failures were encountered during the rc1 build. There is fix queued for the wic selftest issue, the other -lsb kernel module test sanity failures are still being investigated.
>   *   Many fixes for issues were merged into master including some of the 'random' failures, thanks to all who've worked on them!
>   *   The rc1 build is being put through tests by QA
>   *   Prelink looks like it may be broken in release for non FHS/LSB library setups
>   *   A successful fido 1.8.1 point release build was queued for QA, 2.0 is taking priority
>   *   Now the sstate issue is fixed, a 1.7.3 build will also be made soon as autobuilder time is available.
>   *   Reminder:
>      *   We have renamed YP 1.9 to YP 2.0.
>      *   The current version that is in development will launch as YP 2.0 in October, 2015.
>      *   The release name for YP 2.0 is 'jethro'.
> 
> Key YP 1.9/2.0 Dates:
> YP 2.0 Final - 2.0 Cut off: Sept. 28, 2015 noon GMT (rc1 build in QA)
> YP 2.0 final Release Target: Before Oct. 30, 2015
> 
> Key Status Links for YP:
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status
> https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule
> https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features
> 
> Tracking Metrics:
>             WDD 2170 (last week 2165 )
> (https://wiki.yoctoproject.org/charts/combo.html)
> 
> [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
> INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
> *   Work Telephone:          (503) 712-0534
> *    Cell:                                (208) 244-4460
> * Email:                             stephen.k.jolley@intel.com
> 
> 
> 
> 


  reply	other threads:[~2015-10-02 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 15:26 Yocto Project Status WW40 Jolley, Stephen K
2015-10-02 16:10 ` akuster [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-30 15:26 Jolley, Stephen K
2016-09-30 16:16 ` akuster

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=560EAC5A.4020204@mvista.com \
    --to=akuster@mvista.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 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.