HowTo:Make A Bug Report - Revision history

Wfpokorny: Update notes related to Flyspray to Github issue migration.

2018-01-04T18:17:20Z

Update notes related to Flyspray to Github issue migration.

Wfpokorny: Cleanup.

2017-01-24T13:35:11Z

Cleanup.

Wfpokorny: Updating this section for github issues over our older FlySpray issue tracker.

2016-11-19T12:25:35Z

Updating this section for github issues over our older FlySpray issue tracker.

Clipka at 23:07, 24 March 2013

2013-03-24T23:07:57Z

Clipka: /* Text formatting tips */

2013-03-12T18:44:31Z

Text formatting tips

Clipka: added "Text formatting tips" subsection

2013-02-23T11:09:45Z

added "Text formatting tips" subsection

SharkD: link to related article

2010-06-25T21:26:02Z

link to related article

Chrisc: /* Guidelines for opening new tasks */

2009-05-08T18:59:41Z

Guidelines for opening new tasks

Chrisc: /* Guidelines for opening new tasks */

2009-05-08T18:54:45Z

Guidelines for opening new tasks

Chrisc: /* Guidelines for opening new tasks */

2009-05-08T18:52:59Z

Guidelines for opening new tasks

@@ Line 2: / Line 2: @@
 <p>Bug reports are an essential part of development, and the developers need you to let them know about programming defects in POV-Ray. However, there are a few things that you need to keep in mind when you are thinking about submitting a bug report or requesting a new feature. Please take a few moments to read this brief list of guidelines ''before'' you open a new task in our [https://github.com/POV-Ray/povray/issues Github Issue Tracking System].</p>
-<p class="Note"><strong>Note:</strong> We are in the process of porting issues still open in our previous [http://bugs.povray.org/ FlySpray Bug Reporting System] to the new
+<p class="Note"><strong>Note:</strong> All issues still open in our previous [http://bugs.povray.org/ FlySpray Bug Reporting System] have been ported to the new [https://github.com/POV-Ray/povray/issues Github Issue Tracking System]. Please exclusively use Github for new issues and updates to open issues.</p>
 ===== Guidelines for opening new tasks =====
@@ Line 22: / Line 21: @@
 * To quote some other comment, use the github quote feature after marking the text to be quoted.
 * To make code, use the mark code feature of github after marking your code.
-* Refer to github issues and pull request by number prefixed with # and github will create the link. Please refer to older Flyspray tasks not yet ported by their numeric id preceded by "<tt>FS#</tt>" (e.g. <tt>FS#123</tt>) and perhaps insert the URL for as github will create the corresponding link.
+* Refer to github issues and pull request by number prefixed with # and github will create the link. Please refer to older Flyspray tasks by their numeric id preceded by "<tt>FS#</tt>" (e.g. <tt>FS#123</tt>) and perhaps insert the URL for as github will create the corresponding link.
 * Do make use of the preview button.

@@ Line 3: / Line 3: @@
 <p class="Note"><strong>Note:</strong> We are in the process of porting issues still open in our previous [http://bugs.povray.org/ FlySpray Bug Reporting System] to the new
-[https://github.com/POV-Ray/povray/issues Github Issue Tracking System]. During this transition it is necessary to review <em>both</em> systems to know if an issues has already been made known to the developers. Please open all <em>new</em> issues in the [https://github.com/POV-Ray/povray/issues Github Issue Tracking System]. If a FlySpray issue is marked as 'tracked on github' please make any further comments or updates on github.</p>
+[https://github.com/POV-Ray/povray/issues Github Issue Tracking System]. During this transition it is necessary to review <em>both</em> systems to know if an issue has already been made known to the developers. Please open <em>new</em> issues in the [https://github.com/POV-Ray/povray/issues Github Issue Tracking System]. If a FlySpray issue is marked as 'tracked on github' please make further updates on github.</p>
 ===== Guidelines for opening new tasks =====

@@ Line 1: / Line 1: @@
 =====  Reporting bugs in POV-Ray =====
-Bug reports are an essential part of development, and the developers need you to let them know about programming defects in POV-Ray. However, there are a few things that you need to keep in mind when you are thinking about submitting a bug report or requesting a new feature. Please take a few moments to read this brief list of guidelines ''before'' you open a new task in our [http://bugs.povray.org/ Bug Reporting System].
+<p>Bug reports are an essential part of development, and the developers need you to let them know about programming defects in POV-Ray. However, there are a few things that you need to keep in mind when you are thinking about submitting a bug report or requesting a new feature. Please take a few moments to read this brief list of guidelines ''before'' you open a new task in our [https://github.com/POV-Ray/povray/issues Github Issue Tracking System].</p>
 ===== Guidelines for opening new tasks =====
@@ Line 7: / Line 10: @@
 * We cannot accept bug reports for modified versions of POV-Ray.
 * In almost all cases where a rendering bug is being reported, we require a minimal sample scene causing the bug be submitted, as well as an image showing the problem.
-* Always perform a search on '''both open and closed''' bugs ('tasks') before opening a new one. Your bug might already have been reported, or your feature requested.
+* Always perform a search on '''both open and closed''' 'issues' or 'tasks' before opening a new one. Your bug might already have been reported, or your feature requested.
 * Use the English language in any tasks you open.  Nothing will get done if we can't understand you.
 * Only report one bug or request one feature per task.
 * If you report a bug, and we mark it as 'requires testing', then please test it and add a comment to the task telling us how well it works.
-* If a task is closed and marked 'fixed in devel', then try the development version before requesting that it be re-opened.
+* If a task is closed as fixed then try the [https://github.com/POV-Ray/povray/releases development version] before requesting that it be re-opened.
-* If we deny your request to re-open a task, check the History tab for our reason.  If you are unsatisfied with the reason, you are welcome to discuss it in the [http://news.povray.org/ forums].
+* If we deny your request to re-open a task, check the history/comments for our reason. If you are unsatisfied with the reason, you are welcome to discuss it in the [http://news.povray.org/ forums].
 * Be polite.  Remember that you got POV-Ray for free.
 ===== Text formatting tips =====
-Flyspray allows for a lot more formatting within task descriptions and comments than what the buttons give you. Here are a few helpful essentials:
+Github allows for a lot more formatting within task descriptions and comments. Here are a few helpful essentials:
-* To quote some other comment, place a greater-than sign (<tt>></tt>) at the beginning of each paragraph.
+* To quote some other comment, use the github quote feature after marking the text to be quoted.
-* If Flyspray interprets part of your text as formatting where it shouldn't, enclose that text in double percent signs (<tt>%%</tt>...<tt>%%</tt>).
+* To make code, use the mark code feature of github after marking your code.
-* Refer to other Flyspray tasks by their numeric id preceded by "<tt>FS#</tt>" (e.g. <tt>FS#123</tt>); this will automatically create a corresponding link.
+* Refer to github issues and pull request by number prefixed with # and github will create the link. Please refer to older Flyspray tasks not yet ported by their numeric id preceded by "<tt>FS#</tt>" (e.g. <tt>FS#123</tt>) and perhaps insert the URL for as github will create the corresponding link.
 * Do make use of the preview button.
 ===== Miscellaneous =====
-* To illustrate your bug report or comment with images, please do make use of the "attach a file" functionality, rather than linking to some 3rd party image hosting site. This way the image will remain accessible as long as the bugtracker entry.
+* To illustrate your bug report or comment with images, test scenes or zip files, please do make use of the "attach file" functionality, rather than linking to some 3rd party image hosting site. This way the uploaded files will remain accessible as long as the github issue persists. Note when uploading scene related files the POV-Ray extensions of .pov and .inc are not supported; needing an additional .txt suffix before upload. Further .tar and .gz files are '''not''' supported as of this writing, but rather only .zip.
 ==See also==
 *[[Knowledgebase:POV-Ray Feature Requests]]

@@ Line 21: / Line 21: @@
 * Refer to other Flyspray tasks by their numeric id preceded by "<tt>FS#</tt>" (e.g. <tt>FS#123</tt>); this will automatically create a corresponding link.
 * Do make use of the preview button.
 ==See also==
 *[[Knowledgebase:POV-Ray Feature Requests]]

@@ Line 19: / Line 19: @@
 * To quote some other comment, place a greater-than sign (<tt>></tt>) at the beginning of each paragraph.
 * If Flyspray interprets part of your text as formatting where it shouldn't, enclose that text in double percent signs (<tt>%%</tt>...<tt>%%</tt>).
 * Do make use of the preview button.
 ==See also==
 *[[Knowledgebase:POV-Ray Feature Requests]]

← Older revision		Revision as of 21:26, 25 June 2010
Line 14:		Line 14:
	* If we deny your request to re-open a task, check the History tab for our reason. If you are unsatisfied with the reason, you are welcome to discuss it in the [http://news.povray.org/ forums].		* If we deny your request to re-open a task, check the History tab for our reason. If you are unsatisfied with the reason, you are welcome to discuss it in the [http://news.povray.org/ forums].
	* Be polite. Remember that you got POV-Ray for free.		* Be polite. Remember that you got POV-Ray for free.
		+
		+	==See also==
		+	*[[Knowledgebase:POV-Ray Feature Requests]]