| Topic | Notes | Follow-up |
|---|
| RC2 Checklist | - No merge warnings / job errors
- All template sections populated including final Release Notes, as appropriate to the project
- Aligned with Style Guide
| All projects due by 11/09 |
| Human Interfaces | - Allowing links to appropriate "Using ONAP" content of wiki for R1: Portal, SDC, CLAMP, Policy, VID
- Will be restricted to project-specific PTL and Doc team (Greg & Rich)
| Open JIRA Issue(s) opened for resolution during R2 |
| Cutover Branching Strategy | Master vs. Project level branching / tagging | Decision pending | Readthdocs Structure- Recommendation: Leave everything in Master, just don't links to active projects (e.g. AAF, OOM, VVF)
- Branch same day or within 1-2 days after release date
- LF recommends branching only - no tagging except when eliminating a branch
- Limiting sub-modules going forward
| Need to confirm with LF staff (Gildas?) what all projects will be doing |
| Milestones / Enhancements | - Hierarchy clean-up
- Spell out project names & Consistent headings
Address during Release 2?- "Carrier Grade" usability - what does that mean for Documentation?
- Establish formal gating milestones in D2
| Open JIRA Issue(s) for R2 |
| APIs | - REST API
- HealthCheck API
- Components API (eg Java class API)
| Open JIRA Issue(s) for R2 |
| 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)
Current: | LF pursuing Quarter 1, 2018 |