https://sourceforge.net/p/vteddy/wiki/HowToReportIssues/Recent changes to HowToReportIssuesenWed, 21 Jan 2015 14:13:40 -0000https://sourceforge.net/p/vteddy/wiki/HowToReportIssues/<div class="markdown_content"><pre>--- v1 +++ v2 @@ -2,7 +2,7 @@ We know that if we give software for public use, we will probably receive some bug reports. First, we would thank you for your feedback and your effort to make our products even better. Through our forum, you can submit bug reports, send out patches or request enhancements to developer tools. -[Click here to access vteddy forum!](http://forum.vteddy.com/ "vteddy forum") +**[Click here to access vteddy forum!](http://forum.vteddy.com/ "vteddy forum")** Please, don't submit reports that: </pre> </div>FedericoWed, 21 Jan 2015 14:13:40 -0000https://sourceforge.net56538d1700002b5f9dd2b88dbeddf3724559bc1fhttps://sourceforge.net/p/vteddy/wiki/HowToReportIssues/<div class="markdown_content"><h4 id="how-to-report-issues">How to report issues</h4> <p>We know that if we give software for public use, we will probably receive some bug reports. First, we would thank you for your feedback and your effort to make our products even better. Through our forum, you can submit bug reports, send out patches or request enhancements to developer tools.</p> <p><a class="" href="http://forum.vteddy.com/" title="vteddy forum" rel="nofollow">Click here to access vteddy forum!</a></p> <p>Please, don't submit reports that:</p> <ul> <li>say nothing ("It doesn't work!")</li> <li>make no sense</li> <li>don't give enough information</li> <li>give wrong information</li> </ul> <p>And please verify before that reports are not about problems that turn out:</p> <ul> <li>to be user error</li> <li>to be the fault of somebody else's program</li> <li>to be network failures</li> </ul> <p>Keep in mind that if a developer is able to reproduce the bug, the bug is very likely to be fixed. If the steps are unclear, it might not even be possible to know whether the bug has been fixed.</p> <p>We would like to receive reports that comply with these directives:</p> <ul> <li><strong>Be specific</strong>: say what you did precisely, it always matters.</li> <li><strong>Be verbose</strong>: give more information rather than less. Don't say too much, but neither too little, because we will probably have to come back and ask more questions.</li> <li><strong>Be careful of pronouns</strong>: don't use words like "it", or references like "the window", when it's unclear what they mean.</li> <li><strong>Read what you wrote</strong>: after writing the report, read it again and see if you think it's clear. If you have listed a sequence of actions which should produce the failure, try following them yourself, to see if you missed a step.</li> </ul></div>FedericoWed, 21 Jan 2015 14:13:09 -0000https://sourceforge.netd908ff4ca2f7f697b7d8da22edd1e5f4dfcb9893