[oe] OE 2011.03 release vs. oe-core migration

[Stefan Schmidt]

Hello.

On Wed, 2011-01-26 at 10:44, Graeme Gregory wrote:
> On 26/01/2011 10:23, Stefan Schmidt wrote:
> >
> > 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.

Great

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

Frans was saying something along these lines as well and personally I would be
happy with one last release with the current metadata layout. This would allow
current OE users to have a release with the latest changes as a base until we
found our way through the oe-core changes moving forward.

Should we try a freeze for the repo this time or go ahead with the model from
last time. Having a branch with fixes which gets deleted once the release taggin
is done?

Depending on some other factors I might also be interested in using this release
for a product and I'm thinking about having a branch for it with fixes and
pooling resources on it. Not much thinking about this yet though.

regards
Stefan Schmidt