There have been member request (http://cards.linaro.org/browse/DEVPLAT-98) to point out what repositories and changes get pulled into the Android build.
The idea we are going with is to write tools/scripts which not only add description to all the git projects used in our builds but also pull them into the month end release notes.
Attached in this bug report are 4 json files which contain description of projects used across our Android builds:
1) git_description_glo.json --> Description of projects pulled from git.linaro.org
2) git_description_aglo.json --> Description of projects pulled from android.git.linaro.org
3) git_description_lpglo.json --> Description of projects pulled from linaro-private.git.linaro.org
4) git_description_hglo.json --> Description of projects pulled from hisilicon.git.linaro.org/landing-team/hisilicon
Here is the json template I have used for descriptions:
------------------------------
{
"name": "<RELATIVE_PROJECT_PATH_GOES_HERE">,
"branch": [
{"name": "<BRANCH_NAME", "description": "<DESCRIPTION>"},
{"name": "<BRANCH_NAME2", "description": "<DESCRIPTION>"}
]
},
------------------------------
Note: BRANCH_NAME(s) is optional. If it is missing it means that the description stands true for all the branches.
In git_description_aglo.json, if a project is a Linaro addon/extra project e.g. "binutils-current" then I have specifically mentioned in its description that it is a "Non AOSP" project. e.g.:
-----------------------------
{
"name": "toolchain/binutils-current",
"branch": [
{"description": "Non AOSP project. Collection of various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation."}
]
},
-----------------------------
It doesn't look neat but it gives us flexibility of marking that project a non-AOSP project while scanning through its git description and preparing the release doc. Open for discussion on this.
I have pushed manifest description files at http://