User Tools

Site Tools


release_process

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
release_process [2017/02/16 09:11]
Uze Choi
release_process [2017/02/16 09:13] (current)
Uze Choi
Line 18: Line 18:
 ^Milestone ​ ^ Date  ^ Detail^ ^Milestone ​ ^ Date  ^ Detail^
 |Feature Spec/API Freeze |-12W|No more breaking changes in API beyond this point. This is done so other developers who are building on top of APIs (e.g. samples, other high level language bindings etc.) can be confident of platform stability| |Feature Spec/API Freeze |-12W|No more breaking changes in API beyond this point. This is done so other developers who are building on top of APIs (e.g. samples, other high level language bindings etc.) can be confident of platform stability|
-|Feature Freeze |-6W|   ​+|Feature Freeze |-6W| Release branch cut and release testing starts at this point. ​ Master branch is open for the next release feature work. Only bug fixes allowed beyond this point on the release branch. New feature requests beyond this point are punted to the next release or it is well understood that taking them for this release may impact dates for subsequent milestones. ​
-|P1 Bug Only |-2W|   ​+|P1 Bug Only |-2W| P1 bugs only at this point. Bug bar moves up steadily (generally weekly) culminating in recall class only by Code Freeze date. 
-|Code Freeze |-1W|   ​+|Code Freeze |-1W|End of bug fixing and start of final test pass for the release. ​ Only recall class fixes taken beyond this point.
-|QA Complete |-1D|   ​+|QA Complete |-1D|Final test pass complete and product is approved ‘ready for release’
-|Release ​    ​|D-Day| ​  ​|+|Release ​    ​|D-Day|Release is tagged and final bits are released to the web|
  
  
release_process.txt · Last modified: 2017/02/16 09:13 by Uze Choi