Page Comparison

Current state

We need processes (and preferably only a single process) that address the needs of our different audiences. Upstream developers are clearly one target audience. target audiences:

• OPNFV developers who work with upstream projects
• NFV developers who want to use OPNFV as a standard platform, or to test new hardware platforms
  
• Service providers who want to test and benchmark different hardware
  
• (What other groups do we need to serve and what are their needs?)

The current release model which starts from the latest stable versions of upstream projects can produce stable releases

The current OVP program assumes a reference platform containing only released upstream versions & which passes all planned compliance tests.  

Issues with current state

An approach could be a process based on the CI evolution - a stepwise qualification for additional testing until an appropriate level of confidence is reached. Artifacts for different audiences can be taken from different stages of this pipeline. i.e. the process would be to determine when we want to make artifacts available from which stage of the pipeline, and what does that imply for the allocation of testing resources to the different pipeline stages at a given time. .

Alternatives

Proposal

https://etherpad.opnfv.org/p/release-process2.0

Next steps

Cloud native VNFs will need to extend CI to CD, some projects (e.g. Clover) are already working these aspects. We should start to think in this direction for the whole OPNFV process to include CD.
Any new resource requirements?

...