Show bugs.wml syntax highlighted
#include "header.wml" select=bugs
#use wml::std::tags
<subject "On reporting bugs">
<p>If you find a problem in Gzz, we would like to hear about it.
<p>The way to inform us of a problem in Gzz is reporting a bug.
#You can do this using your web browser as described below. But please
#follow the following instructions first.
<h2>On making a good bug report</h2>
<p>First of all, see if you can reproduce that bug. This means that
you should be able to list the actions required to trigger the bug
again. We love bug reports that have precise (and preferably simple)
instructions for reproducing the bug, but if you can't reliably
reproduce the bug, report it anyway and tell us that you can't
reproduce it reliably.
<p>
Then, look at the first line(s) of output that your Gzz client
prints out, before it opens any windows. They should look roughly like
this:
<pre>
Starting gZigZag client, build: Official 0.5.1 (without modules)
</pre>
or like this:
<pre>
Starting gZigZag client, build: Official Debian package version 0.5.1-1
</pre>
or like this:
<pre>
Starting gZigZag client, build: Official CVS snapshot 2000-08-10T19:17:01Z
(without modules)
</pre>
or like this:
<pre>
Starting gZigZag client, build: Custom CVS Build 2000-08-08T12:35:25Z
by ajk@musti
</pre>
The specifics of those lines will vary but the general format is the
same. You should copy these lines precisely into your bug report so
we know which version you are using. (If you have made local changes
to the sources, please tell us about them too.)
Then, if you have any ideas on the cause or a possible fix for the
bug, include them in your bug report.
<h2>How to report the bug</h2>
<p>Mail your report to <a
href="mailto:zzdev@xanadu.net">zzdev@xanadu.net</a>. Remember to
specify in your mail subject that you are reporting a bug in Gzz.
#<p>First, check if the bug you've found is already reported. There is
#<a href="http://sourceforge.net/bugs/?group_id=513">a list of known
#bugs in GZigZag</a>; check that list first.
#<p>We recommend that you <a
#href="http://sourceforge.net/account/login.php">log in to
#SourceForge</a> before submitting your bug. It will allow you to get
#email notifications about our activities regarding the bug report. If
#you do not have a SourceForge account, you can <a
#href="http://sourceforge.net/account/register.php">create one</a>.
#You can report bugs even without a SourceForge account, but then you
#will not get any emails about your bug.
#<p>When you've checked that the bug is not in the bug list (and you
#have logged in if you want to do that), go to <a
#href="http://sourceforge.net/bugs/?func=addbug&group_id=513">the bug
#reporting page</a>. For now, ignore the category and bug group items.
#Write a one-line summary of the problem in the <em>Summary</em> text
#box. Then write a detailed account of the problem in the
#<em>Details</em> text box. Finally, press the <em>Submit</em> button.
See more files for this project here