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

[Lauren Post]

> 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.

> Lastly, I'm not able to clone fsl-arm-yocto-bsp.git.  When I run:
> git clone git://git.freescale.com/imx/fsl-arm-yocto-bsp.git

The manifest is only meant for repo init - not for git cloning.  It is a just a basic repo so that we don't have to package our manifest in a release package as we did for earlier releases with i.MX with Yocto Project.

Lauren Post
Freescale i.MX Yocto Project team lead