...
| Name | Topic/task | Outcome |
|---|---|---|
Andreas Geißler |
| Updated our Working Review List (Copy of Guilin Documentation (working version for reviews)) |
Andreas Geißler |
|
|
Release requirement for documentation | 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 | |
Outdated/not maintained content |
...
https://zoom.us/j/92987486389?pwd=QUdnMVVjZS83Y0dEalA2Y01UQzhEZz09
Document List (Work in progress for Hackathon):
...
Project Name
...
Document Owner
(name - use @ notation)
...
Current Document State (as of M1)
Choices:
- New
- Maintained
...
Activity Planned for Release
Choices:
- Initial Publication
- Major Update
- Minor Update
- No Change
...
Preliminary Documentation
New docs or new projects ONLY
(enter "N/A" if not applicable, or link to gerrit if completed)
...
Attended Doc Hackathon 1 on <date>
(Document owner must attend at least one hackathon)
(fill in green checkmark 
if attended)
...
Attended Doc Hackathon 2 on <date>
(Document owner must attend at least one hackathon)
(fill in green checkmark if attended)
...
Reviewed by the doc project (reviewed means release related content. Such as release notes and release name were applicable)
By best effort!
...
M1
...
M2/M3
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
ittay , automatically generated
...
...
...
...
...
...
...
...
...
...
Event Client Documentation Repository
...
...
...
...
...
...
...
...
release notes
API
...
...
...
...
...
...
MOD User guide
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
https://docs.onap.org/en/latest/guides/onap-developer/developing/index.html
https://git.onap.org/doc/log/docs/conf.py
...
...
...
...
...
...
...
...
...
...
...
...
...
...