Update issue templates (#1932)

.github/ISSUE_TEMPLATE/help_wanted.md

@@ -1,5 +1,5 @@
 ---
-name: Help wanted
+name: Open to contribution
 about: A maintainer specific template
 title: ''
 labels: help-wanted 

.github/ISSUE_TEMPLATE/new_release.md

@@ -32,9 +32,12 @@ Release Candidates :
 - [ ] Locally test the prerelease on macOS (Silicon)
 - [ ] Locally test the prerelease on Windows
 - [ ] Locally test the python wheels on Linux
-- [ ] Locally test the python wheels on macOS (Intel)
+- [ ] Locally test the python wheels on macOS (Silicon)
 - [ ] Locally test the python wheels on Windows
-- [ ] If it fails, fix the issues in `release` branch, copy this paragraph and increment `N`
+- If it fails,
+ - [ ] Fix the issues in `release` branch,
+ - [ ] Edit this issuethis paragraph and increment `N`
+ - [ ] Merge F3D release into master: https://github.com/f3d-app/f3d/compare/master...release
 - [ ] Else proceed to the next part
 
 Release :
@@ -53,6 +56,8 @@ Release :
 - [ ] Communicate on hackernews
 - [ ] Communicate on linkedin
 - [ ] Communicate on mastodon
+
+- [ ] Merge F3D release into master: https://github.com/f3d-app/f3d/compare/master...release- [ ] Communicate on bluesky
 - [ ] Move all issue from current milestone to next milestone, close current roadmap issue and open a next roadmap issue
 - [ ] Update `doc/dev/ROADMAPS_AND_RELEASES.md` for next release
 - [ ] Create an issue for updating dependencies in CI and superbuild
@@ -62,13 +67,15 @@ Linux testing protocol:
 - Install F3D-X.Y.Z-RCN-Linux-x86_64-raytracing system wide
 - `f3d testing/data/cow.vtp` -> check render, orientation, press R and check raytracing
 - `f3d testing/data/f3d.stp` -> check render, orientation
+- `f3d testing/data/f3d.glb` -> press "Space", check animation is going smoothly and takes 4 seconds
 - `f3d /path/to/any/new/file.format` -> check render
 - `rm -rf ~/.cache/thumbnails`
 - `pcmanfm` (or another supported file manager)
 - Check that all supported files in testing/data have a generated thumbnails, especially for new file formats if any
 - Double click on supported file in testing/data, especially for new file formats if any and check it opens in F3D
 - Drag&Drop cow.vtp, Drag&Drop palermo_park.hdr, check render
 - Check that CTRL+O (file dialog) is working
+- Press "Esc" and check the following commands `reload_current_file_group`, `set_camera top`, `toggle_volume_rendering`, `exit`
 - `cd examples/libf3d && mkdir build && cd build && cmake ../ && make`
 - `./cpp/check-engine/check-engine`
 - `./cpp/render-interact/render-interact ../../../testing/data/cow.vtp`
@@ -77,10 +84,12 @@ macOS testing protocol:
 - Install F3D-X.Y.Z-RCN-macOS-x86_64-raytracing.dmg
 - Double click on cow.vtp, check render and orientation, press R and check raytracing
 - Double click on f3d.stp, check render and orientation
+- Double click on f3d.glb, press "Space", check animation is going smoothly and takes 4 seconds
 - Double click on any new supported file.format, check render
 - Check all supported file in testing/data directory in finder have the f3d mark, if not, check that "open with" suggest F3D
 - Drag&Drop cow.vtp, Drag&Drop palermo_park.hdr, check render
 - Check that CTRL+O (file dialog) is working
+- Press "Esc" and check the following commands `reload_current_file_group`, `set_camera top`, `toggle_volume_rendering`, `exit`
 
 Windows testing protocol:
 - Install F3D-X.Y.Z-RCN-Windows-x86_64-raytracing.exe, add F3D to path for all users
@@ -91,8 +100,10 @@ Windows testing protocol:
 - Check that every supported file has a small "f3d" mark, for those that don't check that "Open with" -> "Use another app" suggest F3D.
 - Double click on cow.vtp, check render and orientation, press R and check raytracing
 - Double click on f3d.stp, check render and orientation
+- Double click on f3d.glb, press "Space", check animation is going smoothly and takes 4 seconds
 - Double click on any new supported file format, check render
 - Check that CTRL+O (file dialog) is working
+- Press "Esc" and check the following commands `reload_current_file_group`, `set_camera top`, `toggle_volume_rendering`, `exit`
 - `cd examples\libf3d && mkdir build && cd build && cmake ../ && cmake --build . --config Release`
 - `.\cpp\check-engine\Release\check-engine`
 - `.\cpp\render-interact\Release\render-interact ..\..\..\testing\data\cow.vtp`
@@ -103,8 +114,11 @@ Python testing protocol:
 - python
 ```
 import f3d
-eng = f3d.Engine(f3d.Window.NATIVE)
-eng.loader.load_geometry("/path/to/cow.vtp")
-eng.window.render()
+eng = f3d.Engine.create()
+eng.scene.add("/path/to/cow.vtp")
+eng.window.render() # No effect on Windows
 eng.interactor.start()
 ```
+- Check the following
+ - The name of the window is `f3d` at all time
+ - Python provides suggestions whenever the "Tab" key is pressed