Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Status Update
Date: Wed, 20 Mar 2013 23:45:58 +0000	[thread overview]
Message-ID: <1363823158.16482.131.camel@ted> (raw)

As people know, feature freeze was at the start of the week. I've been
trying to ensure the remaining patches get rounded up and into the
build.

At the same time, the Yocto Project Autobuilder infrastructure has been
undergoing an upgrade to new software. I really wanted this to happen
now as if it doesn't it has to be postponed until after release and we
need features and efficiency in the new codebase.

Unfortunately its highlighted a number of issues, particularly races
and my bandwidth has been sucked into helping trying to fix the sanity
test failures. I have fast tracked some patches into master in the
qemu-testlib code with that in mind since the autobuilder is pretty
critical to how we maintain stability of OE-Core.

This combined with an abnormally high meeting load has meant there are
some things I haven't been able to do. I am unfortunately totally max'd
out atm, people's patience is appreciated.

Cheers,

Richard




             reply	other threads:[~2013-03-21  0:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 23:45 Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-29 20:57 Status Update Richard Purdie
2013-05-07 12:45 Richard Purdie
2013-05-28 17:35 Richard Purdie
2013-05-28 19:34 ` Jack Mitchell
2013-07-01  7:01 Richard Purdie
2014-03-10  2:20 Richard Purdie
2014-03-10  2:43 ` Robert Yang
2014-03-18 13:09 Richard Purdie
2014-03-24 11:53 Richard Purdie
2014-04-01 13:51 Richard Purdie
2014-04-08 12:25 Richard Purdie
2014-04-15 18:45 Richard Purdie
2014-04-29  8:49 Richard Purdie
2014-04-29 11:29 ` Richard Purdie
2014-04-29 17:31   ` Otavio Salvador
2014-10-03 12:01 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=1363823158.16482.131.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