Meeting Content (minutes / recording / slides / other):

April 25th, 2019

Andrew, Sukhdev, Thor Chin

P-SC call at 4PM PT to review API GW proposal from Inswinstack

Agreed to introduce as a feature within a blueprint to allow both standalone deployment and wider deployment into other blueprints.

Both members on the process committee had seen and reviewed the material.

Recommendation to TSC is to approve with the note only one committer has currently been identified.

attendees
- Jim, Tina, Tapio, Andrew, Bill
we reviewed the proposed wording for the use of the name “Akraino” in project titles
- we decided we’ll review this internally…
- “the use of the term Akraino certified BP or FP is restricted to BP or FP that have been verified by the TSC as reaching the minimum level of conformance to the Mature or Core levels”
release 1 milestones
- we’ll add this item to our docket
we started discussing it wrt our Blueprint state table
- how do the two processes fit together?
- RC0, RC1, RC2
  - why 3?
  - Tapio related his experience from OPNFV – need some kind of tracking for sure, but don’t want it too detailed
ideally the milestones would be real tasks, and demonstrable
we brainstormed a list of milestone tasks that we might want to propose
- first deployment in validation lab
- first testing logs shipped up to CI/CD environment
- peer Jenkins is set up & working
- blueprint-specific test plan shared with the Community
- lab is set up for CD
we also discussed that the blueprint should iterate through M3-RC1 as many times as the Blueprint owner thinks makes sense

...