User Tools

Site Tools


release_criteria

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
release_criteria [2017/01/10 07:43]
Uze Choi [Release Exit Criteria]
release_criteria [2017/01/10 08:01] (current)
Uze Choi [Release Entry Criteria]
Line 4: Line 4:
  
   - The release does not contain third party IP (without appropriate license) ​   - The release does not contain third party IP (without appropriate license) ​
-  - IoTivity Member company should run its own static analysis tool on the codes it contributes. If it doesn’t own a tool, SonarQube should be executed+  - IoTivity Member company should run its own static analysis tool on the codes it contributes. ​
   - The OIC specified features are in compliance with Spec, expect feature specified by IoTivity   - The OIC specified features are in compliance with Spec, expect feature specified by IoTivity
-  - Test Plan/​Strategy has been approved by cross functional team members 
-  - All SDK and getting started documentation are ready and reviewed by cross functional team 
   - All supported features are code complete and stable   - All supported features are code complete and stable
-    ​* Features that are partially implemented should be labeled as experimental +    * Any code changes on supported features or APIs will be handled by Jira defect system 
-    ​* Any code changes on supported features or APIs will be handled by Jira defect system ​and considered in Release ​   Exit Criteria) +    * All Supported feature and API should be fixed 6 weeks prior to QA start in case of Major version release 
-    * All Supported feature and API should be fixed within ​6 weeks in case of Major version release+    * Capable of being build in supported environments 
 +  - Release code in single branch and appropriately tagged. 
 +    * Major/​Important minor (or stable) version is to maintain in Release branch 
 +    * Revision (or prior to stable) version is to be released as a snapshot on branches. 
 +  - Test Plan/​Strategy has been approved by cross functional team members
   - All unit test case are executed with pass rate of:   - All unit test case are executed with pass rate of:
     * Feature fully implemented:​ 100%     * Feature fully implemented:​ 100%
Line 17: Line 19:
     * Unit test should cover more than nominal code path (should include nominal and common error handling)     * Unit test should cover more than nominal code path (should include nominal and common error handling)
   - Test devices and test environment are setup and ready   - Test devices and test environment are setup and ready
-  - SDK Test apps and/or sample apps are ready+  - Test apps and/or sample apps are ready
   - Test cases completed, reviewed and approved by cross functional team members   - Test cases completed, reviewed and approved by cross functional team members
-  - Release code in single branch ​and appropriately tagged. +  - All documentation are ready and reviewed by cross functional team 
-    * Major/​Important minor (or stable) version is to maintain in Release branch +  - Triage meeting is required for filtering out the remaining defect
-    * Revision (or prior to stable) version is to be released as a snapshot on branches. +
-  - Capable of being build in supported environments +
 ====== Release Exit Criteria ====== ====== Release Exit Criteria ======
   - Test case are defined & executed per test plan - rate: 100%   - Test case are defined & executed per test plan - rate: 100%
release_criteria.txt · Last modified: 2017/01/10 08:01 by Uze Choi