User Tools

Site Tools


fuel_opnfv_b-wp

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
fuel_opnfv_b-wp [2015/11/01 19:09]
Jonas Bjurel [Work-package 2]
fuel_opnfv_b-wp [2016/02/07 19:48]
Jonas Bjurel [Consolidation]
Line 8: Line 8:
  
 ===== Work-package 1 ===== ===== Work-package 1 =====
 +** Status: CONCLUDED **
 +
 ** Goal: ** ** Goal: **
  
Line 27: Line 29:
 **Due dates:** **Due dates:**
  
-  * Latest date for integrated projects to sign-up for WP1: Thu November 2 -2015+  * Latest date for integrated projects to sign-up for WP1: Mon November 2 -2015
   * Latest date for a partially functional plugin commit (merge is not necessary): Tue Nov 10 -2015   * Latest date for a partially functional plugin commit (merge is not necessary): Tue Nov 10 -2015
   * Latest date for a functional Fuel@OPNFV core demo (Yoytube clip or otherwise): Fri Nov 13 -2015   * Latest date for a functional Fuel@OPNFV core demo (Yoytube clip or otherwise): Fri Nov 13 -2015
Line 33: Line 35:
  
 ===== Work-package 2 ===== ===== Work-package 2 =====
 +** Status: CONCLUDED **
 +
 ** Goal: ** ** Goal: **
  
Line 43: Line 47:
   * Full Kilo/Fuel 7 integration   * Full Kilo/Fuel 7 integration
   * Fully functional plugins based on Kilo/Fuel 7.0   * Fully functional plugins based on Kilo/Fuel 7.0
 +  * Fuel 8.0/Liberty alfa version
  
 **Definition of done:** **Definition of done:**
Line 56: Line 61:
  
 ===== Work-package 3 ===== ===== Work-package 3 =====
 +** Status: CONCLUDED **
 +
 ** Goal: ** ** Goal: **
   * Stable Fuel@OPNFV core rebase to Fuel 8.0/Liberty in experimental branch   * Stable Fuel@OPNFV core rebase to Fuel 8.0/Liberty in experimental branch
   * Fully functional end-system-state plugins integrated with master/Fuel 7.0/Kilo   * Fully functional end-system-state plugins integrated with master/Fuel 7.0/Kilo
   * Soft code-freeze (no further feature code is allowed)   * Soft code-freeze (no further feature code is allowed)
-  * Libert/Fuel 8.0 merged with master branch+  * Fuel 8.0/​Liberty ​merged with master branch 
 +  * stable/​brahmaputra branch created
  
 **Content:​** **Content:​**
Line 72: Line 80:
  
 ===== Work-package 4 ===== ===== Work-package 4 =====
 +** Status: CONCLUDED **
 +
 ** Goal: ** ** Goal: **
   * Hard code freeze   * Hard code freeze
   * Fuel 8.0/Liberty rebase stable builds based on good/bad commit indications from Fuel upstream CI   * Fuel 8.0/Liberty rebase stable builds based on good/bad commit indications from Fuel upstream CI
   * Fully functional end-system-state plugins integrated with master/Fuel 8.0/Liberty   * Fully functional end-system-state plugins integrated with master/Fuel 8.0/Liberty
-  * stable/​brahmaputra branch created 
   * master branch is opened up for C-release development   * master branch is opened up for C-release development
  
Line 89: Line 98:
  
 ===== Consolidation ===== ===== Consolidation =====
-**Content:**+**Dates updated!! ​**
  
-Project release consolidation and stabelization.+**Project release consolidation and stabilization reviews:**
  
-  * (1) Stability ​review 1: Jan 15 -2015 +  * Release ​review 1: Feb 9 -2016 
-  * (1) Stability ​review 2: Jan 22 -2015 +  * Release ​review 2: Feb 11 -2016 
-  * (1) Stability ​review 3: Jan 27 -2015+  * Release ​review 3: Jan 16 -2016 
 +  * Release review 4: Jan 18 -2016 
 +  * Release review 5: Jan 23 -2016 
 +  * Release review 6: Feb 25 -2016 (Final release approval) 
 +  
 +Maintenance reviews will continue until end of life support for Fuel@OPNFV Brahmaputra support
  
-**(1)Stability ​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:+**NoteRelease ​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:
   * Gating commits to the stable branch   * Gating commits to the stable branch
-  * Assigning a task-force team to perform system ​stabelization ​activities/​measures +  * Assigning a task-force team to perform system ​stabilization ​activities/​measures 
-  * Deciding to push features, not enough stable/not meeting enough test coverage to a comming release.  +  * Deciding to push features, not enough stable/not meeting enough test coverage to a comming release. 
- +  * Review of documentation and guidelines. 
-Feature owners/​PTLs ​of integrated projects are expected to participate in the stability reviews, but lack voting rights in case voting is needed.+  * Review and approval ​of deviations 
 +  * Review and approval of maintenance/​service release plan. 
 + 
  
 +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. **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:** Feb -2016+**Due date:**  
 +  ​* Feb 26 -2016: Main release - "​brahmaputra/​sr0"​ 
 +  * TBD: SR1 - "​brahmaputra/​sr1"​ (Likely end March - with released Fuel 8.0 and high-priority bug-fixes) 
 +  * TBD: SR2 - "​brahmaputra/​sr2"​ (Likely end April - with bug-fixes and inclusion of late excluded B-release features)
  
  
fuel_opnfv_b-wp.txt · Last modified: 2016/02/07 19:50 by Jonas Bjurel