Master branch merges

Master branch merges

[Richard Purdie]

We're coming up to an interesting point in the development cycle since a
lot of the feature development work Yocto has been working on is winding
up. It means there are a few significant patches waiting to go into
master.

Typically, life isn't straightforward and this is complicated by the
fact I'll be in a black hole as far as modern communication goes for
Thur/Fri/Sat.

I've given what I should do under these circumstances a fair bit of
thought and currently I'm thinking that the best approach is likely to
merge everything that is ready. This is realistically the only way it
will get the final round of testing.

Its possible something will break. Fixes can easily be shared and queued
up on a branch in my absence and Saul should be able to help with that
if needed.

So this is a conscious decision and we'll see how it works out! :)

Cheers,

Richard

Re: Master branch merges

[Saul Wold]

On 07/27/2011 02:28 AM, Richard Purdie wrote:
> We're coming up to an interesting point in the development cycle since a
> lot of the feature development work Yocto has been working on is winding
> up. It means there are a few significant patches waiting to go into
> master.
>
> Typically, life isn't straightforward and this is complicated by the
> fact I'll be in a black hole as far as modern communication goes for
> Thur/Fri/Sat.
>
> I've given what I should do under these circumstances a fair bit of
> thought and currently I'm thinking that the best approach is likely to
> merge everything that is ready. This is realistically the only way it
> will get the final round of testing.
>
> Its possible something will break. Fixes can easily be shared and queued
> up on a branch in my absence and Saul should be able to help with that
> if needed.
>
To help with this process, if there is patch for an M3 related problem, 
please include M3 in the patch/pull request subject line so I can 
quickly get to those this week.

Thanks
	Sau!

> So this is a conscious decision and we'll see how it works out! :)
>
> Cheers,
>
> Richard
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>