home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
C!T ROM 5
/
ctrom5b.zip
/
ctrom5b
/
OS2
/
BBS
/
GIGP1106
/
REPORT.BUG
< prev
next >
Wrap
Text File
|
1994-08-20
|
3KB
|
60 lines
╔════════════════════════════════════════════════════════════════════╗
║ READ THIS DOCUMENT UNTIL YOU GET ALL THE WAY TO THE END PLEASE!! ║
╚════════════════════════════════════════════════════════════════════╝▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
I am more than willing to look at bug reports. Presently, my time is limited
to actually looking at them, on the weekends, as my normal job consumes much
of my time.
In order to maximize my available time to handle as many bugs and feature
additions as possible, it is absolutely imperitive that these instructions
are followed. I can NOT afford to take the time to go hunting for lose files
that people send, or chasing people who do not give me a complete archive as
per this document - if you can't send me what I need, the file transfer will
have been wasted :-( ..
When sending me bug reports, I will need the following:
o Your *.CFG files.
o Your GATEWAY.MSG file.
o If related to hosting a mailing list, your *.ML files.
o If related to fidonet->usenet, sample .PKT files that
are about to go into the gateway [those are the INPUT files!!!]
o If related to usenet->fidonet, sample .D/.X files from your
spool directory will be needed. Once again, I need
the INPUT files - not the final output.
o A README.1ST file describing the problem.
This is _very_ important - trying to track down netmail
related to a specific file, or vice versa, is very time consuming,
and takes away from how productive I can actually be with GIGO.
o Describe version (dos? os/2? date on .exe?)
o Describe your environment (dos? os/2? dv? windows? _free_ ems?)
o Describe problem or symptons
I can not stress enough the need for this archive to be complete, nor can I
stress enough the need for INPUT files to work with. Output files do me
_no_ good, since they do not let me trace GIGO in operation while running
your configs and your input files. I can not financially afford to go chasing
people who send me incomplete files.
Double check: Do you have all of the above files ready to go?
Good. Place them into an archive, named after your MYSITE variable.
Do NOT call it "bugs.zip" or some such, as I can not identify it that way.
Do NOT send your files "loose" (ie, not in a package), as OTHER PEOPLE are
doing it too, and I have no way to filter things out.
If sending via email or file attach, I can handle zip, zoo, lha, lzh, arj,
pack, and older versions of arc. If sending via FTP, I can also handle
tar, tgz, and tar.Z files.
You may now send your archive to me a variety of different ways:
File attach to 1:203/7707 or 1:203/8055 (Not a misprint)
Email uudecode@wmeonlin.sacbbx.com (keep it under a meg per message)
FTP it to ftp.netcom.com:/pub/jfesler/incoming
Snail mail to 2405 Carta Court #4 | Sacramento, CA 95825 USA
Thank you for reading this far. With your help, we will all appreciate
the increased productivity, which will translate to sooner bug fixes
and enhancements.