Documentation:Windows Section 6 - Revision history

Jholsenback: link changes

2016-10-01T11:11:33Z

link changes

Clipka: indexentry fix

2016-05-03T22:57:07Z

indexentry fix

Chrisc: Indexentry fix

2013-02-11T06:04:32Z

Indexentry fix

Chrisc: /* Crash Upload Utility */

2013-02-02T02:39:30Z

Crash Upload Utility

Chrisc: /* Bug Reports */

2013-01-29T20:49:20Z

Bug Reports

Jholsenback: itc

2011-12-07T05:18:11Z

itc

Jholsenback: cleaning up some validation errors

2011-01-10T14:25:53Z

cleaning up some validation errors

Chrisc: /* Bug Reporting via our Bug Tracking System */

2011-01-02T11:16:51Z

Bug Reporting via our Bug Tracking System

Chrisc: /* Bug Reporting via Email */

2011-01-02T11:15:24Z

Bug Reporting via Email

Chrisc: Remove "Spelling" sub-section.

2011-01-02T11:14:38Z

Remove "Spelling" sub-section.

@@ Line 12: / Line 12: @@
 <p>
-Before submitting any bug reports to our forums, make sure that the bug is not already listed on our [http://bugs.povray.org/ bug tracker].
+Before submitting any bug reports to our forums, make sure that the bug is not already listed on our [https://github.com/POV-Ray/povray/issues issue tracker] on GitHub.
 Please remember that the POV-Ray users who provide assistance on our forums are volunteers who give their time for free so you
 can enjoy this program for no charge. Keep this in mind when wording your message.
@@ Line 43: / Line 43: @@
 ===Bug Reporting via our Bug Tracking System===
 <p>
-Bug reports may be lodged about POVWIN by using the  [http://bugs.povray.org/ bug tracking system]. The bugtracker is monitored regularly by the POV-Ray development team and they will address any properly-lodged bug reports in the most timely manner possible.
+Bug reports may be lodged about POVWIN by using the [https://github.com/POV-Ray/povray/issues issue tracker] on GitHub. The  issue tracker is monitored regularly by the POV-Ray development team and they will address any properly-lodged bug reports in the most timely manner possible.
 </p>

@@ Line 8: / Line 8: @@
 <!--</wikitalk>--->
 ==Bug Reports==
-{{#indexentry:Bug Reports|Reporting bugs}}
+{{#indexentry:Bug Reports}}
 <p>

@@ Line 8: / Line 8: @@
 <!--</wikitalk>--->
 ==Bug Reports==
-{{#indexentry:Bug Reports, Reporting bugs}}
+{{#indexentry:Bug Reports|Reporting bugs}}
 <p>

@@ Line 37: / Line 37: @@
 ===Crash Upload Utility===
-<p> In order to assist the team in tracking down crashes, Structured Exception Handling and mini-dump generation capabilities have been added. After an unhandled exception POVWIN will now offer the option of creating a mini-dump (brief or full) for submission either manually or via the crash upload utility which is installed with the program.
+<p> In order to assist the team in tracking down crashes, Structured Exception Handling and mini-dump generation capabilities have been added. After an unhandled exception POVWIN will now offer the option of creating a mini-dump (brief or full) for submission either manually or via the crash upload utility which is installed with the program. If you want to draw immediate attention to a crash it is strongly recommended that you also post a comment in the [http://news.povray.org/povray.bugreports/ povray.bugreports] or [http://news.povray.org/povray.windows/ povray.windows] forum and provide the crash report ID supplied by the upload utility.
 </p>

@@ Line 11: / Line 11: @@
 <p>
-Before submitting any bug reports, make sure that the bug is not in the list of known bugs
+Before submitting any bug reports to our forums, make sure that the bug is not already listed on our [http://bugs.povray.org/ bug tracker].
-below. Please remember that the POV-Ray users who provide assistance on our news server are
+Please remember that the POV-Ray users who provide assistance on our forums are volunteers who give their time for free so you
-volunteers who give their time for free so you can enjoy this program for no charge. Keep this
+can enjoy this program for no charge. Keep this in mind when wording your message.
 </p>
 <p>
-MAKE ABSOLUTELY SURE that the subject of your report isn't already covered in this document.
+Make sure that the subject of your report isn't already covered in this document.
-Questions that are already answered either in this help file, any README's, installation
+We also <strong>strongly recommend</strong> that you check out the online version of the
 [http://wiki.povray.org/content/Knowledgebase:POV-Ray_Questions_and_Tips POV-Ray Questions and Tips]
 before submitting a report.
 </p>
@@ Line 53: / Line 30: @@
 <p>
-To do this, go to the GUI Extensions menu, and deselect 'Use Extensions'. Then exit and
+To do this, go to the GUI Extensions sub-menu of the Options menu, and deselect 'Use Extensions'. Then exit and
 restart POV-Ray for Windows. The GUI Extensions menu should then state 'No Extensions Loaded'
 (it may already do this if you've got none installed). Then attempt to duplicate the problem
@@ Line 60: / Line 37: @@
 ===Crash Upload Utility===
-<p> In order to assist the team in tracking down crashes, Structured Exception Handling and mini-dump generation capabilities have been added to povray for windows. After an unhandled exception POVWIN will now offer the option of creating a mini-dump (brief or full) for submission.</p>
+<p> In order to assist the team in tracking down crashes, Structured Exception Handling and mini-dump generation capabilities have been added. After an unhandled exception POVWIN will now offer the option of creating a mini-dump (brief or full) for submission either manually or via the crash upload utility which is installed with the program.
 </p>
@@ Line 77: / Line 49: @@
 </p>
-<p>Any messages or reports sent to us may be re-posted in our newsgroups, on USENET, or on our web site, if we consider it appropriate to do so.</p>
+<p>Any messages or reports sent to us may be re-posted in our forums, bug tracker, or our web site if we consider it appropriate to do so. We will in such cases of course remove any obvious identifying or personal information first.</p>
 <p>You should not expect any reply to bug reports. If you wish to follow the progress of a bug, it's best to use the bug tracker (be sure to configure your account to receive notifications of replies to your bug). You can also request to be emailed when there are replies to an existing bug report.</p>
@@ Line 88: / Line 60: @@
 <li>The version number of POV-Ray for Windows. You can see this by selecting About from the Help Menu.</li>
-<li>Your operating system. We need to know what version of Windows you are running
+<li>Your operating system. We need to know what version of Windows you are running.
 <li>Your computer ; what processor and how much memory.</li>
@@ Line 94: / Line 66: @@
 <li>A complete description of the problem and what led up to it. It will make it a <strong>lot easier to track a bug down</strong> if you can include a scene file that will cause the problem. If the file is large, try removing parts until you have the minimum scene file that will cause the problem.</li>
 </ol>
 <!--<wikinav>--->

@@ Line 25: / Line 25: @@
 <p>
-We <b>strongly recommend</b> that you check out the online version of the
+We <strong>strongly recommend</strong> that you check out the online version of the
 [http://wiki.povray.org/content/Knowledgebase:POV-Ray_Questions_and_Tips POV-Ray Questions and Tips]
 before submitting a report.
@@ Line 92: / Line 92: @@
 <li>Your computer ; what processor and how much memory.</li>
-<li>A complete description of the problem and what led up to it. It will make it a <b>lot easier to track a bug down</b> if you can include a scene file that will cause the problem. If the file is large, try removing parts until you have the minimum scene file that will cause the problem.</li>
+<li>A complete description of the problem and what led up to it. It will make it a <strong>lot easier to track a bug down</strong> if you can include a scene file that will cause the problem. If the file is large, try removing parts until you have the minimum scene file that will cause the problem.</li>
 </ol>

@@ Line 65: / Line 65: @@
 ===Bug Reporting via Email===
 <p>
-Unfortunately, email bug reporting is no longer available due to the abuse of this facility by a number of users. You may only report bugs in POVWIN by using the bugtracker mentioned in the next section.
+Please use the POV-Ray news forums or the bug reporting system.
 </p>