Openembedded Core Discussions
 help / color / mirror / Atom feed
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 Project Status WW04
Date: Sun, 24 Jan 2016 15:11:29 -0800	[thread overview]
Message-ID: <56A55A21.50504@gmail.com> (raw)
In-Reply-To: <9ADD3FDE8B189B4AA2F8A3C711F8155E56FAE346@fmsmsx111.amr.corp.intel.com>



On 01/22/2016 08:29 AM, Jolley, Stephen K wrote:
> Current Dev Position: YP 2.1 M2
> Next Deadline: YP 2.1 M2 Cutoff (Feature Freeze) date is January 25, 2016 noon GMT
> 
> SWAT team rotation: Randy -> Benjamin
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
> 
> Key Status/Updates:
> 
>   *   Yocto Project 2.0.1 was successfully built and is due out of QA soon, likely to release next week.
>   *   Yocto Project 2.1 M2 cutoff is on Monday, please ensure any patches expected to be in M2 are sent to the mailing list for review before then.
>   *   We are looking pretty up to date with patch review/processing although there is a large queue in -next pending final checks but which should merge soon.
>   *   We are keeping an eye on CVEs and ensuring they get merged to various branches as we can find the bandwidth but we're low on manpower for this.

What CVEs need merging? New ones or ones submitted for stable branches?

- armin


>   *   I'd like to highlight that there are increasing numbers of stack overflow questions about the project and help in providing good answers on there would be appreciated.
>   *   WDD and bug trend continue to rise to new heights. We are simply receiving more bugs than we have resources to fix/close.
> 
> Key YP 2.1 Dates:
> YP 2.1 M2 Cutoff (Feature Freeze) date is January 25, 2016 noon GMT
> YP 2.1 M2 Target release date is February 12, 2016
> YP 2.1 M3 Cutoff (Feature Freeze) date is February 29, 2016 noon GMT
> YP 2.1 M3 Target release date is March 18, 2016
> YP 2.1 M4 / Final Cutoff: March 28, 2016 noon GMT - Stabilization only milestone.
> YP 2.1 Final Release Target: April 29, 2016
> 
> Key Status Links for YP:
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status
> https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule
> https://wiki.yoctoproject.org/wiki/Yocto_2.1_Features
> 
> Tracking Metrics:
>             WDD 2581 (last week 2524 )
> (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
> 
> 
> 
> 


      parent reply	other threads:[~2016-01-24 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 16:29 Yocto Project Status WW04 Jolley, Stephen K
2016-01-22 19:58 ` [yocto] " Philip Balister
2016-01-24 23:11 ` 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=56A55A21.50504@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