Skip to content

Update release issue template to handle latest release procedure #8757

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
joaosaffran merged 6 commits into from
Aug 17, 2026
Merged

Update release issue template to handle latest release procedure #8757

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
a8d62cd
update release issue template to handle latest release procedure
joaosaffran-zz Aug 10, 2026
f5dd18f
Update release.md
joaosaffran Aug 12, 2026
a8fec1e
Adding comments
joaosaffran Aug 17, 2026
40ff97d
Update .github/ISSUE_TEMPLATE/release.md
joaosaffran Aug 17, 2026
9aeed77
Update release.md
joaosaffran Aug 17, 2026
355e18a
Fix NuGet typing
joaosaffran Aug 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion .github/ISSUE_TEMPLATE/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,13 @@ assignees: ''

---


<!--
Some of the steps below might not be required; delete them as appropriate.
Some known scenarios that might require editing include, but are not limited to:
point releases; targeting a specific release, such as a Vulkan SDK only; and preview releases.
-->

# Schedule

- [ ] MM/DD/YYYY - Release branch forks from `main`
Expand All @@ -20,6 +27,7 @@ assignees: ''

# Tasks

<!-- This is only required if the release branch doesn't exist -->
## Before Fork

This part of the release process is to 'prime the pump' - that is to make sure
Expand All @@ -35,6 +43,8 @@ we are confident we can generate builds for the new branch
- [ ] Zip files for github release
- [ ] NuGet package
- [ ] VPack
- [ ] Update SPIRV-Headers and SPIRV-Tools submodules, in the release branch,
to target the commits specified by LunarG.
- [ ] Final merge of `main` into the release branch

## After Fork
Expand All @@ -45,12 +55,14 @@ we are confident we can generate builds for the new branch
## Quality Sign Off

- [ ] Microsoft Testing Sign-off (@damyanp)
- [ ] Google Testing Sign-off (@s-perron / @Keenuts)
- [ ] NVIDIA Testing Sign-off (@dnovillo / @pow2clk)

## Release

- [ ] Tag final release and post binaries
- [ ] Add the new compiler to Compiler Explorer
- [ ] Email LunarG the release tag and update the release spreadsheet.

@alsepkow Alex Sepkowski (alsepkow) Aug 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this still apply to all spot releases/releases? I think it will only apply to when we are doing a release alongside LunarG?

@joaosaffran joaosaffran Aug 10, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it only applies for when we are releasing alongside LunarG. However this issue doesn't seem to distinguish between different releases. For example, it doesn't specify what is part of a spot release or a full release.

@alsepkow Alex Sepkowski (alsepkow) Aug 10, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's because we weren't consistently creating issues for spot releases before. Maybe now is a good time to add the differentiation? Or maybe it's obvious enough when it doesn't apply

@V-FEXrt Ashley Coleman (V-FEXrt) Aug 12, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably have a different issue for each. Or maybe a branch within the issue. I've done a number of point releases using the release issue and its always awkward

@joaosaffran joaosaffran Aug 13, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the idea of having a different issue for point releases, but I still think that those will have a bunch of branches within them, depending on where we release and what we are releasing.

@damyanp Damyan Pepper (damyanp) Aug 13, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already have too many issue templates, I'm not keen on adding another one. I think instructions to "delete as appropriate" or maybe being able to list some as "point release only" or "major release only" would work.

Another tool we have is that we can put HTML comments or other instructions into the template - it's reasonable to expect the person creating the new release to have to edit / customize it a bit. We already expect them to fill in the dates, for example.

@joaosaffran joaosaffran Aug 17, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added some minor comments pointing Damyan Pepper (@damyanp) suggestions

- [ ] Publish the new compiler NuGet package.


[^1]: [Ask Mode](https://devblogs.microsoft.com/oldnewthing/20140722-00/?p=433)
Expand Down
Loading