Talking with @praneethbajjuri it seems like we want to unify release documents for all OS sections under a single device specific document. This means that software revisions should match and if they do not then the tables should be updated to indicate version deviations. This is probably better suited to a reduction of information, such as simply listing tags instead of the current tag, branch, and build config. https://github.com/TexasInstruments/processor-sdk-doc/blob/master/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst#build-information
In this scheme OS's will be harder to prune and update so it will be up to individual contributors to validate their changes by making sure all files listed in TOC with multi-os information are updated.
Any concerns or ideas?
Talking with @praneethbajjuri it seems like we want to unify release documents for all OS sections under a single device specific document. This means that software revisions should match and if they do not then the tables should be updated to indicate version deviations. This is probably better suited to a reduction of information, such as simply listing tags instead of the current tag, branch, and build config. https://github.com/TexasInstruments/processor-sdk-doc/blob/master/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst#build-information
In this scheme OS's will be harder to prune and update so it will be up to individual contributors to validate their changes by making sure all files listed in TOC with multi-os information are updated.
Any concerns or ideas?