All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jolley, Stephen K" <stephen.k.jolley@intel.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Minutes: Yocto Project Technical Team Meeting - Tuesday, June 7, 2016 8:00 AM US Pacific Time
Date: Tue, 02 Aug 2016 08:23:49 -0700	[thread overview]
Message-ID: <1470151429.3175.189.camel@linux.intel.com> (raw)

Attendees: Saul, David Wolfe, Joshua, Belen, Ross, Mark, Bill
 
Agenda:
* Opens collection - 5 min (Stephen)
* Yocto Project status - 5 min (Stephen/team)
.	YP 2.2 M1 took longer to release 
        - Stabilize it
        - Performance issues
	   - GCC, GTK, Python3
        - Number of high bugs
        - Released
        YP 2.2 M2
        - selftest patch
        - Completed QA
          Higher number of bugs across multiple areas
        - Fixed Performance issues
          Kernel enabled DEBUG which increased size and time
          Parsing linux-yocto-dev increased time.
        YP 2.2 M3 is the final milestone for enhancements
        - M3 Closes on Aug 29th
	YP 2.1.1
        - rc1 is getting QA'ed now
        - Possible release next week pending QA completion
        YP 2.0.3 Planning
        - Has about 20 patches since 2.0.2 release
        - Possible post 2.2 timeframe (November)

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
* Opens - 10 min
	Package Manager for 2.2 and beyond
        - probably smart for 2.2
        - looking into dnf for future
        Kernel Version will be either 4.7 or 4.8
        - Waiting for 4.8 rc2/3 and check with GregKH
        Poky - LTS/LTM Branch
        - Community Driven
        - 2 Years
        - Companies continue to push on older branches that they are
interested in.
        - Most patches would be in Oe-Core meta-data

* Team Sharing - 10 min
 RP has branch with multi-config in parallel
  - fixes various other tools
  - Distributed builds in 2.2 is unlikely due to resource constraits

Thanks,
 
Sau!


             reply	other threads:[~2016-08-02 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 15:23 Jolley, Stephen K [this message]
2016-08-03 13:19 ` Minutes: Yocto Project Technical Team Meeting - Tuesday, June 7, 2016 8:00 AM US Pacific Time Philip Balister
2016-08-03 15:17   ` akuster808
2016-08-09 10:09     ` Anders Darander
2016-08-09 19:36     ` Khem Raj
2016-08-09 20:53       ` akuster808
  -- strict thread matches above, loose matches on Subject: below --
2016-06-07 15:11 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=1470151429.3175.189.camel@linux.intel.com \
    --to=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.