Media
/
compute-runtime
mirror of https://github.com/intel/compute-runtime.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Documentation: Release cadence update 

Update the information about release cadence.
Move from weekly posting, to monthly posting off dedicated release branch.

Signed-off-by: Cetnerowski, Adam <adam.cetnerowski@intel.com>
This commit is contained in:
Cetnerowski, Adam 2022-11-21 13:07:18 +00:00 committed by Compute-Runtime-Automation
parent 811db4d575
commit 26f7452fe5
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -43,10 +43,14 @@ You may obtain a copy of the License at: https://opensource.org/licenses/MIT
## Release cadence
* Once a week, we run extended validation cycle on a selected driver.
* When the extended validation cycle tests pass, the corresponding commit on github is tagged using
the format yy.ww.bbbb (yy - year, ww - work week, bbbb - incremental build number).
* Typically for weekly tags we will post a binary release (e.g. deb).
_Release cadence changed from weekly to monthly late 2022_
* At the beginning of each calendar month, we identify a well-tested driver version from the previous month as a release candidate for our monthly release.
* We create a release branch and apply selected fixes for significant issues.
* The branch naming convention is releases/yy.ww (yy - year, ww - work week of release candidate)
* The builds are tagged using the following format: yy.ww.bbbbb.hh (yy - year, ww - work week, bbbbb - incremental build number from the master branch, hh - incremental commit number on release branch).
* We publish and document a monthly release from the tip of that branch.
* During subsequent weeks of a given month, we continue to cherry-pick fixes to that branch and may publish a hotfix release.
* Quality level of the driver (per platform) will be provided in the Release Notes.
## Installation Options