You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/release-checklist.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Anyone in the @gfx-rs/wgpu team can perform these steps.
14
14
15
15
Approx 1 Week Before:
16
16
17
-
- Determine if `glow` (@groves), `metal-rs` (@gfx-rs/wgpu) or any other dependant crates will need a release. If so, coordinate with their maintainers.
17
+
- Determine if `glow` (@groves), `rspirv` (@gfx-rs/wgpu) or any other dependant crates will need a release. If so, coordinate with their maintainers.
18
18
- Go through the changelog:
19
19
- Re-categorize miscategorized items.
20
20
- Edit major changes so a user can easily understand what they need to do.
@@ -27,9 +27,10 @@ Day of Release:
27
27
- Bump the wgpu dependency numbers in the following places:
28
28
-`Cargo.toml`
29
29
-`examples/standalone/*`
30
+
-`examples/bug-repro/*`
30
31
- Grep for the previous version to ensure various documentation links are updated.
31
32
- For example, if the previous version was v24.0.0, grep for `v24` and `24.0`
32
-
- Ensure `glow` and `metal` are updated to the latest version if needed.
33
+
- Ensure `glow` and `rspirv` are updated to the latest version if needed.
33
34
- Add a new header for the changelog with the release version and date.
34
35
- Create a PR with all of the version changes and changelog updates.
0 commit comments