Re: Preparing for release - Freeze on master

[Frans Meulenbroeks <fransmeulenbroeks@gmail.com>]

2010/11/16 Khem Raj <raj.khem@gmail.com>:
> On Tue, Nov 16, 2010 at 2:39 PM, Paul Menzel
> <paulepanter@users.sourceforge.net> wrote:
>> Dear OE folks,
>>
>>
>> Am Dienstag, den 16.11.2010, 10:20 -0800 schrieb Khem Raj:
>>
>>> In order to get to the 2010.12 release, I would like to request to
>>> stop pushing any changes to master until release. Please keep your
>>> changes in you local tree ready for when the window
>>> opens again after the release.
>>
>> would it be a good idea, to either have each developer with commit
>> access create his/her own “next” branch or to have a common next branch,
>> where those changes could be published, so that work is not duplicated?
>>
>
> Either way is fine. If its posted to mailing list then it goes to
> patchwork and after approvals I will sweep them
> if devs publish a pull branch thats ok too.
>
>> […]
>>
>>
>> Thanks,
>>
>> Paul
>>
>>
>> PS: Khem, thanks for taking the lead in getting this release done!
>>
>> _______________________________________________

What about new recipes?
I have a few new tasks and a new image that I was planning to add
tonight, but didn't get to it.
Also I will have a working uclibc++ recipe by tomorrow or so. (the
current one does not build for me).
I feel changes like those are pretty harmless.

Frans