Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
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 WW04
Date: Fri, 22 Jan 2016 14:58:40 -0500	[thread overview]
Message-ID: <56A289F0.3070800@balister.org> (raw)
In-Reply-To: <9ADD3FDE8B189B4AA2F8A3C711F8155E56FAE346@fmsmsx111.amr.corp.intel.com>

On 01/22/2016 11:29 AM, Jolley, Stephen K wrote:
>   *   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.

We've been raising this issue the last few OpenEmbedded developer
meetings. There are a few people trying to answer questions there as we
have time. It takes time to build up enough reputation to be useful
there. Please people try and help out with this work. You should be able
to search on OpenEmbedded, Yocto, and Poky and get most of the questions.

Philip


>   *   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
> 
> 
> 
> 


  reply	other threads:[~2016-01-22 19:58 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 ` Philip Balister [this message]
2016-01-24 23:11 ` akuster808

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=56A289F0.3070800@balister.org \
    --to=philip@balister.org \
    --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