...

After the delivery branch is created, we will have a very short delivery team to control the final content of the Release. The delivery Team composed of 1 member representing each project will analyze the impact of every defect and decide its inclusion or not into the delivery release. Jira will be used to support all documentation and decisions.
The Gerrit merge process will be limited to the delivery team.

API Versioning

For the API versioning strategy, refer to: ONAP API Common Versioning Strategy (CVS) Guidelines 

While this addresses a few of the questions below, some thought is required in the relation to a releaseThis requires some more thought. Questions to answer:

• Who assigns version numbers?
• same as for repos. Projects decide
• Where do we track available APIs for a given release ?
• -> we need something that has a similar role to O-Parent
• What’s our policy of depreciating APIs? 
• -> I assume we would require MAJOR API versions to be available for extended periods of time

...