Create an issue template for releases (#7467)

* Create an issue template for releases

* Remove invalid syntax

Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>

---------

Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>

.github/ISSUE_TEMPLATE/release.yml

@@ -0,0 +1,40 @@
+name: Release
+description: Create a new release for the Zoo Design Studio
+title: Cut release v1.?.?
+labels: [release]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        > Instructions: https://github.com/KittyCAD/modeling-app/blob/main/CONTRIBUTING.md#shipping-releases
+
+        ---
+
+        # Manual Checklist
+
+        Release builds URL: ???
+
+        ## Windows via ???
+
+        * [ ] Download the release build for this platform
+        * [ ] Confirm the application opens (dismiss the updater)
+        * [ ] Create a project with a basic Text-to-CAD prompt
+        * [ ] Confirm the result is viewable in an engine stream
+        * [ ] Open the application again and confirm the updater can downgrade
+
+        ## macOS via ???
+
+        * [ ] Download the release build for this platform
+        * [ ] Confirm the application opens (dismiss the updater)
+        * [ ] Create a project with a basic Text-to-CAD prompt
+        * [ ] Confirm the result is viewable in an engine stream
+        * [ ] Open the application again and confirm the updater can downgrade
+
+        ## Linux via ???
+
+        * [ ] Download the release build for this platform
+        * [ ] Confirm the application opens (dismiss the updater)
+        * [ ] Create a project with a basic Text-to-CAD prompt
+        * [ ] Confirm the result is viewable in an engine stream
+        * [ ] Open the application again and confirm the updater can downgrade

CONTRIBUTING.md

@@ -251,7 +251,8 @@ Before you submit a contribution PR to this repo, please ensure that:
 
 #### 1. Create a 'Cut release $VERSION' issue
 
-It will be used to document changelog discussions and release testing.
+Use the **Release** issue template.
+This will be used to facilitate changelog discussions and release testing.
 
 https://github.com/KittyCAD/modeling-app/issues/new
 
@@ -270,27 +271,9 @@ The workflow should be listed right away [in this list](https://github.com/Kitty
 
 #### 3. Manually test artifacts
 
-##### Release builds
-
 The release builds can be found under the `out-{arch}-{platform}` zip files, at the very bottom of the `build-apps` summary page for the workflow (triggered by the tag in step 2).
 
-Manually test against [this list](https://github.com/KittyCAD/modeling-app/issues/3588) across Windows, MacOS, Linux and posting results as comments in the issue.
-
-A prompt should show up asking for a downgrade to the last release version. Running through that at the end of testing
-and making sure the current release candidate has the ability to be updated to what electron-updater points to is critical,
-but what is actually being downloaded and installed isn't.
-If the prompt doesn't show up, start the app in command line to grab the electron-updater logs. This is likely an issue with the current build that needs addressing.
-
-```
-# Windows (PowerShell)
-& 'C:\Program Files\Zoo Design Studio\Zoo Design Studio.exe'
-
-# macOS
-/Applications/Zoo\ Modeling\ App.app/Contents/MacOS/Zoo\ Modeling\ App
-
-# Linux
-./Zoo Design Studio-{version}-{arch}-linux.AppImage
-```
+Assign someone to each section of the manual checklist generated by the issue template.
 
 #### 4. Bump the KCL version