Per the 13 November discussion on this topic, following are some of the thoughts regarding release process improvements for R4+
With R3, a swimlane was added to the release calendar with some modeling milestones.
Based on this, we need to consider additional steps to bring us closer to the realization of a common model and model driven. Following are a few thoughts:
- Tag components that are potentially impacted by an information model (IM) / data model (DM) concept and socialize the concept with that component team (M1)
- The Modeling Subcommittee actively reviews component information flows, looking for I/Os being identified and related to the information model (M3)
- This is an opportunity to reconcile the IM/DM with the component model
- Require components to indicate that they comply with the IM/DM
- Require component teams to socialize their data model with the ONAP Modeling subcommittee (M2)
- Require Modeling subcommittee to sign off on data model.
- Require component DM team to provide a DM document with rationalization to IM (M3)
- Alternative - Collaboratively rationalize
The following checklist was proposed during R2, which is something that could be used.
Proposed M3 Checklist modeling updates discussion
Comments are welcome.
Next steps once we have settled on a proposal could include:
- Socialize with ONAP Architecture
- Socialize with the release project manager
- Present to the TSC for approval.