• 1 Overview
• 2 Scope
  • 2.1 What is this release trying to address?
  • 2.2 Use Cases
  • 2.3 Requirements
  • 2.4 Minimum Viable Product
  • 2.5 Functionalities
    • 2.5.1 Epics
    • 2.5.2 Stories
  • 2.6 Longer term roadmap
• 3 Release Deliverables
• 4 Sub-Components
• 5 Architecture
  • 5.1 High level architecture diagram
  • 5.2 Platform Maturity
  • 5.3 API Incoming Dependencies
  • 5.4 API Outgoing Dependencies
  • 5.5 Third Party Products Dependencies
• 6 Testing and Integration Plans
• 7 Gaps
• 8 Known Defects and Issues
• 9 Risks
• 10 Resources
• 11 Release Milestone
• 12 Team Internal Milestone
• 13 Documentation, Training
• 14 Other Information
  • 14.1 Vendor Neutral
  • 14.2 Free and Open Source Software

...

Resources

Fill out the Resources Committed to the Release centralized page.Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:usecase-ui

Release Milestone

The milestones are defined at the Release Level and Planning: Honolulu and all the supporting project agreed to comply with these dates.

...

The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.

Please refer to Honolulu Documentation

Other Information

• Vendor Neutral

...