Fuel@OPNFV plan for four work-packages and a consolidation period until the Brahmaputra release. Work-package 3 coincide with the overall Brahmaputra official code-freeze (Milestone E). Fuel will apply a soft code freeze policy for the Brahmaputra E-milestone, and will deploy yet another work package (WP4) before the hard code freeze policy is applied. A two weeks' consolidation phase is planned, leading up to the Brahmaputra release.
NOTE: The work-packages does not only involve Fuel@OPNFV project work, but equally important commitments and collaborative work from:
Status: CONCLUDED
Goal:
Content:
Definition of done:
Passing build-, automated deploy- and partially func-test.
Due dates:
Status: CONCLUDED
Goal:
Content:
Definition of done:
Due dates:
Status: CONCLUDED
Goal:
Content:
Definition of done:
Passing build-, install- and part of the full func-test pipe-line.
Due date: Jan 5 -2016
Status: CONCLUDED
Goal:
Definition of done:
Due date: Jan 15 -2016
Dates updated!!
Project release consolidation and stabilization reviews:
Maintenance reviews will continue until end of life support for Fuel@OPNFV Brahmaputra support
Note: Release review is referred to as the process where the Fuel@OPNFV committers review the actual system stability and decides upon corrective actions. Corrective actions could be any of:
Feature owners/PTLs of integrated projects as well as the lead for the Genesis-, Releng-, Functest-, Yardstick- and Pharos project are expected to participate in the release reviews, but others than Fuel@OPNFV committers lack voting rights in case voting will become needed. As usual, TSC has the final say!
Definition of done: Released stable system including documentation, repeatably working ci-pipeline, repeatably passing fun-test, a 48 hours of stability test, release notes with documented deviations.
Due date: