This may help to reduce the number of duplicate reports we get about some (temporarily) frequently reported issues, like the current crash
happening since GLib 2.79/2.80, or the crash happening with older GIMP versions on macOS Sonoma.
This won't be perfect because not everyone will use or read the template, or notice the url in it, or use the url to find and check the
reports, but I count on it getting more known than right now.
* Makes the wording more concise and "first contributor-friendly"
+ Adds info about submitting patches
* Makes the explanation of use cases implicitly mandatory
+ Adds discuss info to facilitate the redation of use cases
Use the same syntax as was already in the bug template because some
people are still leaving out the howto text in the middle of their own
bug/feature description.
Add a note asking bug reporters to test with the latest stable version
of GIMP or with dev code (not with old stable versions).
Also add some labels on bug reports and feature requests.
We realize that gitlab doesn't encourage people to give base information
as software version or operating system.
Issue templates are not perfect but better than nothing.
Michael Schumacher