Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
	yocto <yocto@yoctoproject.org>
Subject: Features in Yocto Project 1.7
Date: Mon, 24 Mar 2014 16:00:43 +0000	[thread overview]
Message-ID: <1395676843.24890.7.camel@ted> (raw)

As development on 1.6 finishes up, its time to think about what we
should be doing in the 1.7 cycle.

I think from my perspective, in 1.7 I'd like to see us looking at
"Developer Workflow". Its a generic topic which I think covered multiple
areas (in no particular order):

* the ADT/SDK and how it intergrates into the rest of the system
* toaster
* python devshell
* exteralsrc.bbclass
* memory resident bitbake
* how a standalone app developer might build an image
* locked sstate

and probably more I'm forgetting.

If anyone does have things they plan to work on, or ideas for things
that should be worked on, please do file enhancement requests in the
bugzilla:

https://bugzilla.yoctoproject.org/

Cheers,

Richard





             reply	other threads:[~2014-03-24 16:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 16:00 Richard Purdie [this message]
     [not found] ` <533058C1.3000102@arm.com>
2014-03-24 16:18   ` [yocto] Features in Yocto Project 1.7 Richard Purdie
2014-03-24 19:40 ` Rifenbark, Scott M
2014-03-25  0:11 ` --conf Was: " Trevor Woerner
2014-03-25  5:50   ` Martin Jansa
2014-03-26 14:33     ` Trevor Woerner
2014-03-26 14:38       ` Otavio Salvador
2014-03-26 20:45         ` Nicolas Dechesne
2014-03-27 16:33           ` Trevor Woerner
2014-03-26 14:46       ` Martin Jansa
2014-03-25 12:22 ` Otavio Salvador
2014-03-25 15:14   ` Mark Hatle
2014-03-25 14:31 ` David Nyström
2014-03-25 15:16   ` Mark Hatle
2014-03-25 17:37   ` [yocto] " Philip Balister
2014-03-27 10:47   ` David Nyström
2014-03-28 15:23     ` Otavio Salvador
2014-03-28 18:00       ` David Nystrom

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=1395676843.24890.7.camel@ted \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox