[meta-freescale] Freescale Linux 3.10.31-1.1.0_alpha release is online

Otavio Salvador otavio at ossystems.com.br
Fri May 30 09:09:35 PDT 2014


On Fri, May 30, 2014 at 11:17 AM, Bob Cochran <yocto at mindchasers.com> wrote:
> On 05/30/2014 09:53 AM, Lauren Post wrote:
>>
>>
>>> For the repo manifest file (default.xml), can you use tag names (e.g.,
>>> yocto-1.6) when possible instead of the SHA for your revision attribute
>>> inside of the project tag?  It
>>> would save some time of having to do a reverse lookup for each revision
>>> attribute (commit) and make the > manifest more friendly.
>>> And how would I figure out why you chose a particular commit that wasn't
>>> otherwise notable / tagged
>>> (e.g., you're not using the 1.6 tag in meta-fsl-arm)?
>>> I looked through the commits in fsl-arm-yocto-bsp.git, but I didn't find
>>> anything to help me with this.
>>
>>
>> When we do code freeze for a release we lock our manifest to specific
>> commit on all layers - many times it is a mid point on the branches past the
>> release.  So unfortunately we can't use a tag or branch name in the
>> manifest.  After we release we go back to the tip and use that for
>> development so our beta release will have more fixes from community from
>> daisy branch.  We always release based on latest official Yocto Project
>> release so 3.10.31 is based off of daisy but will be upstreamed to be part
>> of Yocto Project 1.7.
>
>
> Thanks for the reply Lauren.  I see that you point to the poky revision that
> is indeed at the yocto-1.6 tag, but the meta-fsl-arm revision is not at the
> 1.6 tag.  Other than combing through the mail lists, is there anything
> documented that would help me understand why you picked this particular
> commit for your release?  (the answer is probably obvious to those that
> aren't playing catch up like me).

This is just the point their did the code freeze; there is no 'reason'
to choose one commit on top of another, just a matter of timing.

meta-fsl-arm was tagged after as we were with some ongoing work being
finished. So it was not in 'sync' with YP 1.6 tag.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


More information about the meta-freescale mailing list