You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Topics, Notes, and Follow-Up Tasks
| Topic | Notes | Follow-up |
|---|
| Release / Branching Strategy | - Amsterdam branch will include only project repos that have been formally tagged by LF. Project repos that still need to be tagged:
- Integration
- Logging
- OOM
- VNF Guidelines
- VNF Requirements
- New / updated documentation will always be in the master
- Latest version will always be in readthedocs
| - Submit Request(s) to LF to tag project repos for Amsterdam (per LF must come from project Committer or PTL?)
|
| Wiki Migration | Sub Tasks for: - Setting Up ONAP
- Integrating with ONAP
- Using ONAP
- Architecture
- Documenting ONAP
- Developing ONAP
| New JIRA Issue |
| Structure Clean-Up | - Developing ONAP: Structure and Headings clean-up
| New JIRA Issue |
| Carrier Grade | - "Carrier Grade" usability - what does that mean for Documentation?
- Insuring standards/consistency across projects (e.g. terminology, monitoring, clustering)
- Usability (e.g. Designer, VNF Providers, Operations)
| New JIRA Issue |
| APIs | - REST API
- HealthCheck API
- Components API (eg Java class API)
| New JIRA Issue |
| Glossary | Modeling team responsible - Definitions to RsT
- Indexing / tagging to enable Searching
| Address during Release 2 Create JIRA issue - Greg follow up |
| Tooling / Utilities documentation | How to: - Gerrit guide
- Guidelines (Builds, etc.)
- Utilities: Jenkins, Conversion tools (e.g. LFPandocs)
| New JIRA Issue
(LF pursuing Quarter 3, 2018) |
