From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE 2011.03 release vs. oe-core migration
Date: Wed, 26 Jan 2011 10:44:19 +0000 [thread overview]
Message-ID: <4D3FFB03.9010206@xora.org.uk> (raw)
In-Reply-To: <20110126102308.GA29416@excalibur.local>
On 26/01/2011 10:23, Stefan Schmidt wrote:
> Hello.
>
> During last OEDEM we set out a timeline for quarterly releases. The first one
> hit on time in december 2010 (Thanks Khem).
>
> The next one would be scheduled for 2011-03. As our plans towards oe-core are
> getting into shape I wonder if and how these both are going to conflict.
>
> Will we go ahead and make the 2011-03 release, maybe the last one before moving
> over to oe-core? Personally I don't think these two block each other. Syncing
> would be needed, but people will keep working on the OE repo for a bit longer
> anyway I would think.
>
> If we are going to scratch the release what would be the next target for it?
> Yocto 1.0 is planned for April 2011. Somehow I doubt we will have oe-core ready
> for this in time, including yocto movs to it and we base the rest of OE on top
> of it. Am I wrong here and that is the actual plan?
>
>
My opinion is 2010-03 should be the last release on the old source tree.
Releases after this should be on the new oe-core layer system. I don't
think we should scrap the release as its going to take some time to kick
oe-core into shape and finish the poky merge. Then there is work on
meta-openembedded and meta-distro to do on top of that.
Graeme
next prev parent reply other threads:[~2011-01-26 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 10:23 OE 2011.03 release vs. oe-core migration Stefan Schmidt
2011-01-26 10:44 ` Graeme Gregory [this message]
2011-01-26 11:12 ` Stefan Schmidt
2011-01-26 13:18 ` Frans Meulenbroeks
2011-01-26 14:55 ` Tom Rini
2011-02-07 16:08 ` Stefan Schmidt
2011-02-07 19:36 ` Khem Raj
2011-02-07 19:50 ` Tom Rini
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=4D3FFB03.9010206@xora.org.uk \
--to=dp@xora.org.uk \
--cc=openembedded-devel@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.