Re: OpenEmbedded Release 2010.12 --- needs your help!

[Martin Jansa <martin.jansa@gmail.com>]

On Fri, Nov 05, 2010 at 10:22:38AM +0100, Eric Bénard wrote:
> Le 05/11/2010 07:52, Martin Jansa a écrit :
> > what about branching future release those 2-3 weeks ago and keep master for
> > active development?

no new recipes during at least last week of stablizing was also proposed
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-November/026552.html

> Stabilizing the master branch is active development as this allows to have
> stronger fundation for the next features you can introduce 2 or 3 weeks after 
> the stabilization weeks starts.

I agree but pushing new recipes to master and cherry-picking of fixes
from master to "next release" would also work and even allow testing of
fix.patch in master before cherry-picking it.

> > I know it could lower number of people using this future release branch
> > during testing period before release, but still seems better then pushing 3
> > weeks of commits from my local branch as soon as release is branched and
> > master open for new recipes again.

> That's the way linux, u-boot & co are running and when the new merge window
> opens several thousand of patches can be merged in a few days.

And also why there is linux-next, but I agree that in our scale we can keep new
recipes and features in local checkouts/out-of-tree branches without too
much pain in merging them after 3 weeks.

> If we don't do that, the idea of stable release which implies detecting and 
> fixing potential failures introduced by previous big changes will fail.

IMHO forcing main branch to be closed for new stuff (gcc branches after
stage1, before opening stage1 for new version) is used mostly to force
developers to use branch which is supposed to become stable without
tracking only the latest.

But as I said before I don't mind (much) keeping new recipes locally for
those few weeks or even pay more attention to my not-embedded-related daywork
instead of playing with OE :).

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com