All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Feature Freeze
Date: Mon, 16 Feb 2015 17:36:57 +0000	[thread overview]
Message-ID: <1424108217.25541.4.camel@linuxfoundation.org> (raw)

I have to admit I've lost track of time a bit however the calender says
Milestone 3 (M3) finishes this week and that marks "feature freeze" for
the release. Beyond this point we have M4 which which is targeted for
bug fixing only, no extra features and no package upgrades in general.

I'm therefore looking at the list of things we'd like to get into 1.8
and trying to figure out what is missing. The things I'm thinking we'd
prefer to get in, *if* we can are:

Upgrades:
* Bluez v4/v5 switch (in master-next testing)
* Upgrade to glibc (assuming it builds and don't regress anything)
* Pulseaudio 6.0 (related to bluez in particular)
* Python 2.7.3 -> python 2.7.9 upgrade (long overdue and nearly ready)

Enhancements:
* kernel-dev: make Kconfig audit output visible (#6943) since this 
  impacts our user experience
* Extended SDK containing development workflow tools
* Further integration of build-compare for package feed maintenance

Bruce: Are we at the right kernel versions we want for release for qemu
for example?

I get the feeling there may be some pieces I've forgotten, please let me
know if so. Whilst M3 technically closes now, there are probably a few
more days, as time moves forward its going to become harder to convince
me to take things though.

Cheers,

Richard





             reply	other threads:[~2015-02-16 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 17:36 Richard Purdie [this message]
2015-02-16 17:55 ` Feature Freeze Bruce Ashfield
2015-03-04 15:20 ` Burton, Ross
2015-03-04 15:20   ` [OE-core] " Burton, Ross

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=1424108217.25541.4.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.