Page Comparison

• Complete the list of existing documents (Guilin Documentation)
• Add git project reference to list
• Possible automation for list... (maybe via Jenkins)
• Verify list with PTLs, if incomplete

• Put to TSC agenda to come up with a Release strategy.
  
  
• Add for each project a release branch,....

We need to create clear requirements for release documentation. Each project need to be aware of what's expected and this need to be tracked by the release manager.

Suggestion to create a table with projects categorised with associated documentation forming an initinal set of release documentation