-----------------------------------------------------------------------------
	Reporting Bugs
-----------------------------------------------------------------------------


First, before you report a bug, check the 'STATUS' file for the product
you are reporting a bug for, and see the 'Known bugs' section in that
file.  If the bug you wish to report is already listed, please don't
report it unless you have extra information to report that may be helpful
for fixing it.

To report bugs:

Send mail to shaggy@csh.rit.edu
with the subject:  BUG: solo-0.96	(if reporting a SOLO bug)
	or:  BUG: shagos-0.52		(if reporting a Shag/OS bug)

(substitute the correct product name and version number for the bug
 you are reporting, if neither of these matches what you're reporting)


In the bug report, please include as much information as possible
about the conditions leading to the bug, as well as any ideas
you have about about why the bug occurred.

If you have already looked at the source and know how to fix
the bug, please send me the fixes as well.

Anyone who helps me fix bugs will get their name 
added to my "Bug-Fixers" listing, which will be distributed
with future releases. (provided they were the first person to 
offer such help)

Also, include the type of machine the bug occurred on, including model,
CPU type and speed, RAM size, and any device configuration information
that might be relevant.  (keep in mind that devices that aren't even
directly relevant could be conflicting with the ones the
bug is occuring with)

If the bug occurs during configuration, please include the type
and version of 'make' you are running, along with the compiler info
and any information about programs the makefile uses that appear
to be failing.  This will help me find the problem much faster.
If you are running older software, try upgrading, and see if the 
problem goes away.  Even if it now works, please send me a bug
report anyway, stating that there is a problem with some older version
of software, and that it now works with the newer version, so that
I can document this for future releases.

If you have the chance to test this software on other different
machines, please do so, and let me know whether or not the bug showed
up on those machines as well.  This will help me figure out what went wrong.
Also, let me know if the bug is reproducible.  If so, please tell me how
to produce it.  If not, describe in as much detail as possible what
happened before the bug occurred.



Remember, to find known bugs:

Look for the STATUS file in the relevant project directory.
This will contain information about the current release, including
a list of bugs, and features that will be added in the future.

Bugs and features marked with an 'o' are important ones that
I intend to deal with as soon as possible.
Those marked with a '-' are ones that I will get around to
eventually if there's time.  (or if I have suddenly get the urge
to do so)
 
If a particular bug or feature is of special interest to you,
please let me know, and if there is enough interest, I will make
those features a higher priority.



Please:

Even with any other correspondance, you should include, in the subject,
at least the package name of the version you currently have
to greatly speed my chances of replying soon.  Any mail regarding my
software that does not have the package and version number in the header
will probably not be replied to very quickly.
 
i.e.:	Subject: boot loader ideas (solo-0.95)


