Release tarballs are a bit pointless and misleading for the main project release when you stop and think about it. I'd like to propose we stop shipping them and by default direct users to use the release branch instead using a git checkout. This mainly means changing the docs. Why? * With the tarball you can't easily update to the next point release (git pull) * You don't have any history which is useful * You can't see your local changes (git diff) * You can't reset local changes easily and probably many more.
Interesting change of strategy. Yes, the docs will be affected by this.
I am working through the YP docs to make these changes. The ripple effect requires a thorough look. So far, I have completed the changes to the YP Quick Start, which can be found here: http://www.yoctoproject.org/docs/1.6/yocto-project-qs/yocto-project-qs.html. Scott
Hi, I have worked through all the manuals and made appropriate changes to de-emphasize use of tarballs for setting up poky and meta-intel. I can't really list all the areas touched as there were many. I suggest loading the mega-manual (http://www.yoctoproject.org/docs/1.6/mega-manual/mega-manual.html) and searching on "tarball". That will hit most of the areas and also have some false hits as well. I put the status of the bug in review mode and will let it ride a while before marking it RESOLVED. thanks, Scott
gahh... forgot to update the status to 'IN PROGRESS REVIEW'
This bug has been in review for quite sometime with no activity. I have addressed all the areas so I am marking it RESOLVED and turning the doc flag to "Done". Scott
Hi Richard, Scott, Is there any effort from QA to be done to verify this? Thanks, Alex.
I suggest QA scan through the mega-manual (http://www.yoctoproject.org/docs/1.6/mega-manual/mega-manual.html) and look for the word "download" and/or "tarball" and/or "release" to get a feel for the areas that talk about getting the software. Scott