All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster <akuster@mvista.com>
To: yocto@yoctoproject.org
Subject: Re: Yocto Project Status WW24
Date: Mon, 13 Jun 2016 09:02:18 -0700	[thread overview]
Message-ID: <575ED90A.6020901@mvista.com> (raw)
In-Reply-To: <9ADD3FDE8B189B4AA2F8A3C711F8155E57185190@fmsmsx111.amr.corp.intel.com>



On 06/10/2016 08:21 AM, Jolley, Stephen K wrote:
> Current Dev Position: YP 2.2 M1
> 
> Next Deadline: YP 2.2 cut off: June 13, 2016 [3 days - Monday!]
> 
> 
> SWAT team rotation: Jussi -> Maxim
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
> 
> 
> Key Status/Updates:
> 
> *        We continue to see various python v3 issues however these are on the most part comparatively minor.
> 
> *        The Centos 7 auobuilder issues look to have been caused by XFS, switching to ext4 seems to have resolved it.
> 
> *        We're expecting some large patchsets for toaster bootstrap v2 -> v3 and changes to move OE-Core/Sato to gtk3+, am hoping to get these into M1.
> 
> *        Richard is starting a discussion on multi-configuration builds on the openembedded-architecture list.
> 
> *        YP 2.0.2 was released last week
> 
> *        We're now working on 2.1.1 with trial builds in preparation for a release

Can I get a sense of when this might happen? when is a code freeze for
this. I am wondering if I have time for another pass through master and
submitted patches. As the Yocto Project follows a more formalized
process, I am hoping I can get a heads up on when a new release is going
to happen.

- armin
> 
> *        2.2 M1 is due next week
> 
> 
> Key YP 2.2 Dates:
> 
> *        YP 2.2 M1 cut off would be: 6/13/16
> 
> *        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 2599 (last week 2622)
> 
> (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!]
> 
> 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-06-13 16:02 UTC|newest]

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

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=575ED90A.6020901@mvista.com \
    --to=akuster@mvista.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.