[meta-freescale] Please review the proposal of FSL Yocto layers reorg

[McClintock Matthew-B29882]

On Thu, Feb 28, 2013 at 8:32 AM, Bob Cochran <yocto at mindchasers.com> wrote:
> On 02/27/2013 04:07 PM, McClintock Matthew-B29882 wrote:
>>
>> On Wed, Feb 27, 2013 at 3:03 PM, Otavio Salvador
>> <otavio at ossystems.com.br> wrote:
>>>
>>> On Wed, Feb 27, 2013 at 5:57 PM, McClintock Matthew-B29882
>>> <B29882 at freescale.com> wrote:
>>>>
>>>> On Wed, Feb 27, 2013 at 2:08 PM, Bob Cochran <yocto at mindchasers.com>
>>>> wrote:
>>>>>
>>>>>
>>>>>>
>>>>>> The FSL Yocto layers reorg proposal is attached, can you please take a
>>>>>> look? Any comment and suggestion is welcome and appreciated.
>>>>>>
>>>>>
>>>>> Thanks Zhenhua.  I have a few questions and comments about your slides.
>>>>>
>>>>> *** Slide 2: "Move all FSL specific layers to totally open source, or
>>>>> as
>>>>> much as possible"
>>>>>
>>>>> I'm all for this.  Will this include your PowerPC Linux Tree?  I didn't
>>>>> see
>>>>> mention of this in your slides.  This can be found today on your public
>>>>> git,
>>>>> but it hasn't been updated in months.
>>>>>
>>>>> I assume there's lots of kernel activity (as can be witnessed on the
>>>>> linuxppc-dev at lists.ozlabs.org list), so I'm assuming an internal Linux
>>>>> tree
>>>>> is being patched often.  It would be great to be able to see your Linux
>>>>> tree
>>>>> patched as issues are being discussed & resolved on yocto & ozlabs mail
>>>>> lists.
>>>>
>>>>
>>>> We work on the upstream tree and also release an SDK kernel tree
>>>> that's fully tested. The layers tend to use the latter since it
>>>> supports all features. Nothing stopping users from adding a version
>>>> using the upstream tree.
>>>
>>>
>>> And from now on, what are the plans?
>>
>>
>> Same using SDK kernel release, I don't think the kernel team will ever
>> have everything upstreamed for an SDK release and supporting all
>> feature and bug fixes. Besides we will pick a kernel and test and fix
>> it so it will always fall out of sync. (e.g. latest kernel release - 1
>> release + fixes)
>>
>>>
>>>>> **** Slide 3: "FSL Layers maintained in git.am.freescale.net,
>>>>> gitfrescale.com, and git.yoctoproject.org"
>>>>>
>>>>> Is your goal to have these layers in sync?  Today, I can find a
>>>>> meta-fsl-ppc
>>>>> layer on yoctoproject and at git.freescale.com.  However, they are not
>>>>> in
>>>>> sync, and I have no idea why one is patched and one isn't.
>>>>
>>>>
>>>> They are somewhat in sync.
>
>
>
> That's today.  What about next week or next month?  As Zhenhua develops the
> revised Yocto layer strategy, I ask that he clarifies the policy on how the
> same named tree on different servers will be maintained.
>
>
>
>
> The ones on git.freescale.com are still
>>>>
>>>> denzil based for the last SDK release. Ones on git.yoctoproject.org
>>>> are newer and include danny and master branches as well.
>>>
>>>
>>> And what are the plans regarding the SDK?
>
>
>
> Can we get a statement in the Yocto layers reorg doc on how each SDK branch
> will be maintained between SDK releases?  As a developer working to get
> products out the door, will I view the patched SDK branch (between releases)
> as a bug fixed SDK or as an experimental branch for the next SDK release?

I understand the sentiment but I don't think we can guarantee anything
here. This is all done for free after all. I understand that's not a
great answer but there are always limited resources spread around.

Upstream / public branches will try to work with all Yocto releases,
while SDK releases could contain a lot of hacks to more things
working, or pre-release things out there door.

-M