From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Release status (M3 feature freeze)
Date: Thu, 03 Sep 2015 11:52:22 +0100 [thread overview]
Message-ID: <1441277542.24871.106.camel@linuxfoundation.org> (raw)
The end of last week was supposed to be feature freeze. We're still
trying to get through the backlog of patches and we continue to see new
random/weird build failures, particularly in the runtime testing. I do
have a rough idea of the things I'm planning to take at this point, or
at least strongly consider:
* systemd upgrade (assuming tests are fixed)
* extensible SDK patches (pending review)
* devtool changes
* sstate signing
* rpm signing
* kergoth's sanity test for file ownership
* package feed comparison (build-compare)
* persistent /var/log
* consider the gcc 5.2 default change
* pseudo upgrade if we can fix the opkg issues
* midori/ephipany replacement
* initramfs/qemu improvements from Patrick
There are a number of changes in master-next which are looking ready too
(pending the current build results). If there is a feature you want to
see in 2.0 and its not listed above, let me know ASAP.
Cheers,
Richard
reply other threads:[~2015-09-03 10:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1441277542.24871.106.camel@linuxfoundation.org \
--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 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.