Page History

...

• Serve different audiences requiring a different trade-off between recent/stable out of the same process (e.g. "Developers" and "End Users")
  • The maturity of each installed version can vary, but it should be clear for the user how well tested the installed version is
•  It should be possible to uniquely identify the installed version
• Every installation of the OPNFV stack should produce the same end result
• The maturity of each installed version can vary, but it should be clear for the user how well tested the installed version is
  
  

...

However, there are still several open questions. The proposal is to set up a working group to define the release process

https://docs.google.com/presentation/d/1YURd7MAhcf2Vx-KTg7zdiavdDVTB8hnY0C2vHFLldE4/edit#slide=id.g37f06ebc6e_0_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?

...