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
fuel_opnfv_b-wp [2016/02/07 19:37]
Jonas Bjurel [Work-package 3]
fuel_opnfv_b-wp [2016/02/07 19:50]
Jonas Bjurel [Consolidation]
Line 80: Line 80:
  
 ===== Work-package 4 ===== ===== Work-package 4 =====
 +** Status: CONCLUDED **
 +
 ** Goal: ** ** Goal: **
   * Hard code freeze   * Hard code freeze
Line 96: Line 98:
  
 ===== Consolidation ===== ===== Consolidation =====
-**Content:**+**Dates updated!! ​**
  
-Project release consolidation and stabelization.+**Project release consolidation and stabilization reviews:**
  
-  * (1) Release review 1: Jan 5 -2016 +  * Release review 1: Feb 9 -2016 
-  * (1) Release review 2: Jan 15 -2016 +  * Release review 2: Feb 11 -2016 (GMRC 1 Aproval) 
-  * (1) Release review 3: Jan 22 -2016 +  * Release review 3: Jan 16 -2016 
-  * (1) Release review 4: Jan 27 -2016 +  * Release review 4: Jan 18 -2016 (GMRC 2 Aproval) 
-  * (1) Release review 5: Feb -2016 (Final release approval) +  * Release review 5: Jan 23 -2016 
-  * (1) -- Reviews ​will continue until end of life support for Fuel@OPNFV Brahmaputra support ​--+  * Release review 6: Feb 25 -2016 (Final release approval) 
 +  
 +Maintenance reviews ​will continue until end of life support for Fuel@OPNFV Brahmaputra support
  
-**(1): 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:+**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:
   * 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.   * Review of documentation and guidelines.
Line 121: Line 125:
  
 **Due date:​** ​ **Due date:​** ​
-  * Feb -2016: Main release - "​brahmaputra/​sr0"​ +  * Feb 26 -2016: Main release - "​brahmaputra/​sr0"​ 
-  * TBD: SR1 - "​brahmaputra/​sr1"​ (Likely ​mid March - with released Fuel 8.0 and high-priority bug-fixes) +  * 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 critical ​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