microsoft / microsoft/DirectXShaderCompiler

Point Release 1.10.2605

Open
#8,741 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
3.7k
Forks
900
Avg merge
2d 11h
Merged PRs (30d)
44

Description

Schedule

  • MM/DD/YYYY - Release Candidate 1 (begin Ask Mode[^1] for release branch).
    • At this point, cherry-picked changes must be approved by @microsoft/hlsl-release
  • MM/DD/YYYY - Final Release Candidate
  • 08/12/2026 - Target Release Date

Tasks

Before Build

This part of the release process is to 'prime the pump'—that is, to make sure
that all the various parts of the engineering system are set into place so that
we are confident we can generate builds for the new branch

  • Internal branches and build pipelines configured
    • Verify that the engineering system can build:
    • Zip files for github release
    • NuGet package
    • VPack
  • Final merge of main into the release branch

After Build

  • Update README.md if necessary

Quality Sign Off

  • Microsoft Testing Sign-off (@damyanp)
  • SPIRV Testing Sign-off

Release

  • Tag final release and post binaries

[^1]: Ask Mode
is a Microsoft-ism to denote when changes require approval before accepting
merges. For DXC this will require approval from @microsoft/hlsl-release

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the release checklist and README.md, then review the release branch, build pipelines, and the required GitHub release outputs: zip files, NuGet, and VPack. The release is done when testing sign-offs are recorded, the final tag is created, and the binaries are posted.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
release
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.