Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
	yocto@yoctoproject.org
Subject: Yocto Project 1.4 Planning Process
Date: Wed, 03 Oct 2012 17:03:46 +0100	[thread overview]
Message-ID: <1349280226.18301.50.camel@ted> (raw)

Whilst I appreciate people are concentrating on 1.3, we do also need to
think about planning 1.4.

https://wiki.yoctoproject.org/wiki/Yocto_1.4_Features

is seeded with the 1.4/Future targeted enhancement requests from the
bugzilla. This is currently unsorted/unprocessed other than some guesses
from the triage team and I doubt we can actually do everything listed
there but there are plenty of good ideas.

If people can see anything that is missing from those lists which they
think is something we should consider working on in 1.4, I'd recommend
filing enhancement requests in the bugzilla so they're included in the
list.

In about a week's time, I'll be sitting down with this list and talking
with the project stakeholders about what resources are available and
which tasks we could use those resources on and generally figure out
what we're going to target in 1.4. If there are resources available I'm
unaware of, please do talk to me btw! :)

Equally, I'd also ask that if there are things you're planning to do in
the 1.4 timescale, please indicate this with an entry in the bugzilla
which you take ownership of, give a rough time estimation/ETA of and set
the status to ACCEPTED. This tells others that you're working on
something and gives us an idea of what changes to expect and when. This
is useful for planning things like demos and the beta testing.

Questions are more than welcome, as is feedback about this process.

Cheers,

Richard







             reply	other threads:[~2012-10-03 16:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 16:03 Richard Purdie [this message]
2012-10-03 16:20 ` Yocto Project 1.4 Planning Process Marcin Juszkiewicz

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