From: Saul Wold <sgw@linux.intel.com>
To: Yocto Discussion <yocto@yoctoproject.org>
Subject: Minutes: Yocto Project Technical Team Meeting - Tuesday, July 5, 2016 8:00 AM US Pacific Time
Date: Tue, 05 Jul 2016 08:25:25 -0700 [thread overview]
Message-ID: <1467732325.6912.229.camel@linux.intel.com> (raw)
Attendees: Saul, Richard, Randy, Armin, Joshua
Agenda:
Yocto Project:
- YP 2.2 M1 Build has gone through QA
- Issues with Toaster and Eclipse
- WIC Issues but not blockers
- Planning to release it regardless
- Very front loaded
- Number of enhancements for M1 uncompleted
- Number of bugs is still high
- Python3 issues still surfacing
- Locale issues
- M2 will close on July 18 5:00pm GMT
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
pseudo
- lost Peter Seabach (seebs), maintainer of pseudo
- Issues still exist in pseudo and master did not resolve
- 2.1.1 Stable Release Status - Armin
- Looking Green, patches merged
- Are we ready to QA and Release?
- A few more patches pending
would be good to have before 11th for QA window
- 2.0.2 Stable Release - Robert
- Patches pending
- pydevshell patch is pending
Opens
Tips and Tricks
- Richard is requesting interesting idea for short blog entries and the
wiki page above is the tracking location, please take a look and add
any thoughts/ideas you might have.
https://wiki.yoctoproject.org/wiki/TipsAndTricks
Randy asked about dropping UClibc, RP replied in affirmative, proposed
dropping main recipe, but not the associated patches in recipes for a
short term and then dropping patches in a future release/recipe updates
next reply other threads:[~2016-07-05 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 15:25 Saul Wold [this message]
2016-07-05 16:03 ` Minutes: Yocto Project Technical Team Meeting - Tuesday, July 5, 2016 8:00 AM US Pacific Time 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=1467732325.6912.229.camel@linux.intel.com \
--to=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 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.