Clarify version info requirements when submitting new issues (IronLanguages#1739)

BCSharp · web-flow · commit 42e6a0ecbf32 · 2023-08-30T09:14:10.000-04:00
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
@@ -1,6 +1,6 @@
 ### Prerequisites
 
-The issue tracker is used to report bugs and request new features, NOT to ask questions.
+The issue tracker is used to report bugs and request new features, **NOT** to ask questions.
 
 Questions should be posted in [Discussions](https://github.com/IronLanguages/ironpython3/discussions/categories/q-a) or to the users mailing list which can be accessed at 
 https://ironpython.groups.io/g/users. 
@@ -19,10 +19,21 @@ https://ironpython.groups.io/g/users.
 2. [Second Step]
 3. [and so on...]
 
-**Expected behavior:** [What you expected to happen]
+**Expected behavior:**
 
-**Actual behavior:** [What actually happened]
+[What you expected to happen]
 
-### Versions
+**Actual behavior:**
 
-You can get this information from executing `ipy -VV`.
+[What actually happened]
+
+### Version Information
+
+If you are using the `ipy` console program, provide output of executing `ipy -VV`. If it is a local build, provide also the git hash of the commit used to build IronPython. Additionally, provide the type of the operating system used.
+
+If you are using the IronPython engine embedded in a .NET application, provide the version number of the NuGet package used (or if it is a local build, the git hash of the commit used to build IronPython), and the following info:
+
+* .NET platform used (choice from: .NET, .NET Core, .NET Framework, Mono, Unity),
+* Version of the .NET platform used,
+* Operating system used,
+* Value of `sys.version`, from imported module `sys`.
