All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: High-level roadmap
Date: Tue, 22 Jan 2013 18:55:49 -0500	[thread overview]
Message-ID: <50FF2705.3@balister.org> (raw)
In-Reply-To: <9779224.vPBlQGNyx7@helios>

On 01/22/2013 01:59 PM, Paul Eggleton wrote:
> Hi all,
> 
> I was recently asked for a high-level roadmap for future releases, and I 
> couldn't find anything to point to on our website. We have this wiki page, but 
> it's somewhat out of date:
> 
>  https://wiki.yoctoproject.org/wiki/Yocto_Project_Roadmap
> 
> Do we have anything else at the moment? If not could something be written up 
> and kept up-to-date?

I think that page updated with the major features added in the releases
to date, combined with features for the next release would be a good
start showing what the Project has done, so people can think about other
ways to make Embedded Development easier.

Philip


      reply	other threads:[~2013-01-22 23:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 18:59 High-level roadmap Paul Eggleton
2013-01-22 23:55 ` Philip Balister [this message]

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=50FF2705.3@balister.org \
    --to=philip@balister.org \
    --cc=paul.eggleton@linux.intel.com \
    --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.