Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Saul Wold <sgw@linux.intel.com>,
	Yocto Discussion <yocto@yoctoproject.org>,
	OpenEmbedded List <openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] Yocto Project Status WW29
Date: Fri, 15 Jul 2016 08:47:55 -0700	[thread overview]
Message-ID: <578905AB.4090701@gmail.com> (raw)
In-Reply-To: <1468596746.6912.772.camel@linux.intel.com>



On 07/15/2016 08:32 AM, Saul Wold wrote:
> 
> Current Dev Position: YP 2.2 M2
> Next Deadline: YP 2.2 M2 cut off would
> be: 7/18/16 (This coming Monday - 5:00pm GMT)
> 
> SWAT team rotation: Paul -> Ross
> https://wiki.yoctoproject.org/wiki/Yoct
> o_Build_Failure_Swat_Team
> 
> Key Status/Updates:
>  * Richard has been out this week, so the report will be thin.
>  * Performance regressions were narrowed down to the GCC6 Update, movingto GTK3 and the Python3 port. Investigation into how to mitigate thisis ongoing.
>  * We’re considering removing uclibc and GCC 5.4 (preferring musl and GCC6) from OE Core 2.2, so if this would impact you please speak up.
>  * 2.1.1 Completed QA, but there was a High found to do with supportingFedora 24, which released very soon after 2.1 initially released andshould be a supported build host. This will delay 2.1.1 until after M2QA is completed.

Any idea on an ETA on M2QA will start. Since 2.1.1 is being delayed,
does that open the door for more back ports not related to the F24 fixes ?

- armin

>  * Reminder that the M2 cut off is this coming Monday!
> 
> Key YP 2.2 Dates:
>  * YP 2.2 M1 release would be: 6/24/16
>  * YP 2.2 M2 cut off would be: 7/18/16
>  * YP 2.2 M2 release would be: 7/29/16
>  * YP 2.2 M3 cut off would be: 8/29/16
>  * YP 2.2 M3 release would be: 9/9/16
>  * YP 2.2 M4 cut off would be: 10/3/16
>  * YP 2.2 M4 release would be: 10/28/16
> 
> Tracking Metrics:
> 	WDD 2698 (last week 2747)
> (https://wiki.yoctoproject.org/charts/combo.html)
> 
> Key Status Links for YP:
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status
> https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule
> https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features
> 
> [If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
> 
> 
> 
> 


      reply	other threads:[~2016-07-15 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 15:32 Yocto Project Status WW29 Saul Wold
2016-07-15 15:47 ` 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=578905AB.4090701@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.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