From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Status Update
Date: Tue, 08 Apr 2014 13:25:27 +0100 [thread overview]
Message-ID: <1396959927.24597.104.camel@ted> (raw)
Executive Summary
=================
Continuing to trend well for release, bug fixes continue to be merged
although patches are starting to get deferred for 1.7 if they're too
risky at this point.
1.6 Release Status
===============
The summary says it all really, bug trends are good but work remains.
The openssl CVE needs to get addresses so we'll probably take a package
upgrade for that specific component.
I am continuing to see a lot of "dubious" patches where the rationale
for the fix doesn't add up. I'm leaning not to take these in those
cases.
Autobuilder
===========
Builds are greenish however we've had a lot of problem with the sanity
tests suffering hung processes. There have also been buildslave issues,
particularly with ab05 which has now been taken out the pool pending
investigation as to why its "upset", so its hard to know if issues are
the hardware or the sanity tests.
Cheers,
Richard
next reply other threads:[~2014-04-08 12:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 12:25 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-15 18:45 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=1396959927.24597.104.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