Skip to content

Latest commit

 

History

History
50 lines (44 loc) · 2.71 KB

RELEASE.md

File metadata and controls

50 lines (44 loc) · 2.71 KB
Raw

Release Process

Intel XPU Backend for Triton releases are aligned to the upstream triton-lang/triton project and to PyTorch. To make a release:

  1. Select a commit common to upstream Triton. Often this commit will be selected by PyTorch at pytorch/.ci/docker/ci_commit_pins/triton.txt. For example:
[FRONTEND] Fix wrong livein set in loop codegen (#4018)
  1. Using git log --graph --oneline find the selected commit in the default branch. Because upstream commits are merged using merge commits, and GitHub displays commits in chronological order, the ordering of commits on GitHub's website cannot be trusted.
* | 23c4cdf1 [intel] Fix bf16 representation
* | e4ac248d Merge commit '445d5edb8a3796b0e6e589682231b2c50fe14871'
|\|
| * 445d5edb [BACKEND] fix bf16 representation in TritonNvidiaGPU and bf16 tl.sort bug (#3975)
* | 0cdcffa2 Merge commit '100e2aaca903ed99564242f933198a6c221d3b50'
|\|
| * 100e2aac [AMD][WMMA] Support dot3d (#3674)
| * 706174da [CI] Add macos build test (#3994)
| * 47f7d45c [AMD] Replace wave with warp where possible. (#3978)
| * d3fb1dc1 [AMD] Move MFMA shortcut check to not compute scratch buffer shape if it is not needed (#3790)
| * b847042d Remove redundant options from passes (#4015)
| * 513f38c4 [FRONTEND] Fix wrong livein set in loop codegen (#4018)
| * d4b16818 [DOCS] improve Triton Linear layout doc (#4005)
* | c37ca9c6 [GEN] Update libGenISAIntrinsics
* | 4d936645 Merge commit '18d691e491b9f6184c505f9b553a49075e67d4bd'
|\|
| * 18d691e4 [BACKEND] Update LLVM version to https://github.com/llvm/llvm-project/commit/10dc3a8e916d73291269e5e2b82dd22681489aa1 (#4010)
| * 1d571390 Remove odd character at beginning of file (#4011)
| * 9d9ec144 [DOCS] fixes to tl.dot (#4006)
* | 8ab1e456 [TritonGEN] Add `triton_gen.cache_controls` operation (#1087)
* | 8b91a5b9 Added new workflow to run pytorch inductor test (#1219)
  1. Checkout a commit from the default branch that is close to the desired upstream commit. In this case, the commit we want is in the middle of a merge. But, this particular commit does not effect any of our code and we don't want other commits from the same merge. So in this case, we will select the last commit before the merge and then cherry-pick our way forward.
git checkout c37ca9c6 # [GEN] Update libGenISAIntrinsics
  1. Next, create a release branch.
git checkout -b release/X.Y.Z
  1. Finally, cherry-pick (or revert) commits to get to the desired state. When cherry-picking, use -x to preserve references:
git cherry-pick -x d4b16818
git cherry-pick -x 513f38c4
  1. Push the release branch to GitHub and start CI pipelines.