All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yocto <yocto@yoctoproject.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Yocto post 1.1 development focus areas?
Date: Thu, 04 Aug 2011 15:54:40 +0100	[thread overview]
Message-ID: <1312469680.14274.8.camel@rex> (raw)

[Cross posted but please reply on the Yocto list]

We're starting to think about the development focus for post Yocto 1.1
and are collecting ideas on the unscheduled feature list on the wiki:

https://wiki.yoctoproject.org/wiki/Yocto_Project_Unscheduled_Feature_List

This is an opportunity for people to mention all the "if only we had X
functionality" ideas they might think of as they use the system.

Obviously there are no promises anything listed will get worked on but
if its not there, the likelihood of it not happening is significantly
higher :)

Cheers,

Richard









             reply	other threads:[~2011-08-04 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 14:54 Richard Purdie [this message]
2011-08-04 19:45 ` Yocto post 1.1 development focus areas? Joshua Lock
2011-08-04 22:38   ` Richard Purdie
2011-08-04 23:27   ` Khem Raj

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=1312469680.14274.8.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yocto@yoctoproject.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.