Key Contacts - Byung-Woo Jun (Ericsson)

Note: The ONAP Streamlining - The Process Release Plan has been approved by ONAP TSC

Marketing version, Montreal, will be scheduled as the previous releases, with following changes (see next two pages for more details)
- Setting release schedule plans for Montreal with Start / RC / Sign off dates only
- The Marketing version will be used as the Major version by ONAP projects
- PTLs decide the minor and patch versions, based on their project release cycles and share the project versioning with TSC
  - provide each project release flexibility and evolution
Integration & Pair-wise testing
- Integration testing will continue to increase ONAP project overall qualities
- Pair-wise testing will continue but it will be based on use cases
- Project testing will be performed by each project team
For Montreal, security scanning will continue as before
Based on feedback during the Montreal, the release plan can be revisited

Marketing release start, RC and Sign off dates will be set (by release manager with TSC approval)
Each PTL determines their project agile cycle(s) based their features
PTLs/Feature owners coordinate with ARCCOM/REQCOM/SECCOM/TSC for the feature review and approval per agile iteration
PTLs/Feature owners may work with OOM, INT and DOC for build, testing and documentation, as needed
Each agile iteration/sprint is reviewed and critiqued by the project team (and ARCCOM/REQCOM/SECCOM/INT/TSC as needed…) and is used to determine what the next step (PTL decides it) until RC
- e.g., priorities, guidance, standards, security…
After Montreal, we may want to revisit the Marketing release RC and Sign off

Define the Marketing Release Start / RC and Signoff plans
Working PTLs, collect each project feature(s) and enhancement(s) to define the Marketing release features and enhancements
- e.g., it i possible to create table(s) that can be filled up by PTLs and/or Release Manager for representing features and enhancements for Montreal
Do not define project development cycle schedules, but write the marketing release contents

Working with the project members, define scope(s) of the project features and enhancements
Determine and manage agile cycle(s) based on the project features and enhancements
Write and check-in project agile-specific documentation (e.g., rst)
Coordinate with ARCCOM/REQCOM/SECCOM/OOM/INT/TSC for the feature/enhancement reviews per agile iteration, as needed
- A way of sharing the project agile cycle process status and results with the Release Manager and ARCCOM/REQCOM/SECOM/OOM/INT/TSC
- Collect input from ARCCOM/REQCOM/SECCOM/OOM/INT/TSC for global requirements and best practices
May work with OOM, INT and DOC for build, testing and documentation, as needed

Define ONAP security and logging global requirements of the Marketing release and agile iteration(s)
Share update with the latest packages upgrades recommendations
Review and provide feedback of project agile iterations from the security perspective, and write security and logging requirement documentation

Support the “ONAP” level common scripts, build, deployment, security & logging configurations
Manage project deployment dependencies and helm charts independencies

Provide ONAP Marketing-level documentation and individual project-level documentation with version control; providing ONAP technical and how-to-use documentation

Provide both Solution-level testing and E2E testing for ONAP project overall qualities