For developers new to Yocto Project the Quick Start Guide is often the first place they pick up guidance on how to develop. The guide refers the release branches and developers are usually unaware that these refer to meta-data data this is changing over time. Imagine two developers Fred and Tim. Fred does a build on a given date and Tim who pulls and builds the meta-data 2 weeks later will likely have a different built. We should explain the Quick Start Guide always points to the best (i.e. bug fixed and CVE applied) meta-data while release tags should be used to keep on a known good build. We should also explain that although release branches have consistent naming across poky, meta-oe, meta-intel (and maybe others?), tags do not.
Henry, I'm taking this bug, and yes, I see what you mean. I will change those two examples so they're checking out on a tag to give them a known spot on the branch and alleviating the "moving target" issue. Kristi
while it may not belong in the quick start guide, I believe the main documentation needs a chapter on branches and tags explaining how both work and what the intent of each is.
Henry - I've updated the relevant sections to use tag checkouts: http://www.yoctoproject.org/docs/temp/yocto-project-qs/yocto-project-qs.html#releases http://www.yoctoproject.org/docs/temp/yocto-project-qs/yocto-project-qs.html#building-an-image-for-hardware Regarding Comment 2, Scott has addressed that in the following dev-manual sections: http://www.yoctoproject.org/docs/2.4/dev-manual/dev-manual.html#checking-out-by-branch-in-poky http://www.yoctoproject.org/docs/2.4/dev-manual/dev-manual.html#checkout-out-by-tag-in-poky Please look this stuff over, and if there are any issues let me know. Thanks Kristi
No feedback in over a month. Presumed correct. Setting to RESOLVED and putting the doc flag to "done." Scott