From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Status Update
Date: Tue, 15 Apr 2014 19:45:01 +0100 [thread overview]
Message-ID: <1397587501.15843.94.camel@ted> (raw)
Changes in the last week
========================
The past week has been turbulent. It seemed we were on track early last
week, then we found some problems. The -rc3 build suffered some build
failures, particularly a sysroot issue with perf. There were also some
BSP issues with beaglebone as well as some QA challenges.
Were able to pull together all the needed fixes quickly and in the end
we built out an -rc4 early, dropping -rc3 since there were too many
known issues. We have now branched although I've not started merging 1.7
patches as yet and hope to hold off for a short while yet.
The biggest problem right now is that beagebone doesn't boot depending
on the directory depth the kernel is built within. We don't understand
why.
I had some issues with email this week. We think of it as instantaneous
but a load of mine disappeared onto the secondary MX and I didn't get it
until after -rc4 was built. This is why some patches didn't get dealt
with so my apologies for that, the timing was particularly unfortunate.
I don't believe we have a reason to stop 1.6 at this point, particularly
if we can document the beaglebone issue. The -rc4 QA report is due soon
and will drive the release decisions.
I've not had much time to spend on 1.7 planning at this point but I'm
hoping to get to that next.
Cheers,
Richard
next reply other threads:[~2014-04-15 18:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 18:45 Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-03 12:01 Status Update Richard Purdie
2014-04-29 8:49 Richard Purdie
2014-04-29 11:29 ` Richard Purdie
2014-04-29 17:31 ` Otavio Salvador
2014-04-08 12:25 Richard Purdie
2014-04-01 13:51 Richard Purdie
2014-03-24 11:53 Richard Purdie
2014-03-18 13:09 Richard Purdie
2014-03-10 2:20 Richard Purdie
2014-03-10 2:43 ` Robert Yang
2013-07-01 7:01 Richard Purdie
2013-05-28 17:35 Richard Purdie
2013-05-28 19:34 ` Jack Mitchell
2013-05-07 12:45 Richard Purdie
2013-04-29 20:57 Richard Purdie
2013-03-20 23:45 Richard Purdie
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=1397587501.15843.94.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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