home *** CD-ROM | disk | FTP | other *** search
/ The Best Internet Programs / BESTINTERNET.bin / internet / qnews / bugs.txt next >
Encoding:
Text File  |  1995-05-15  |  2.6 KB  |  92 lines
  1. QNews Bug Report Form
  2. ---------------------
  3.  
  4. Please complete and mail this form 
  5. to rdavies@magi.com.
  6.  
  7. Due to QNews' downgraded status, problem reports 
  8. filed against v0.9a5 may not be relevant to the
  9. next released version of QNews. 
  10.  
  11. However, if you would like to report major 
  12. functional deficiencies or suggest features 
  13. that you would like to see included in the 
  14. release version of QNews, your feedback will 
  15. be gratefully accepted. 
  16.  
  17.  
  18. Regrettably, the author cannot guarantee individual 
  19. responses to bug reports. 
  20.  
  21. Thanks for taking the time to report this problem.
  22.  
  23.  
  24.  
  25.           Name: 
  26. E-Mail Address:
  27.  
  28.   System Description
  29.   ------------------
  30.  
  31.        CPU (e.g. 486DX-100):
  32.     Amount of system memory: 
  33.         Internet Connection: [ ] SL/IP  [ ] PPP 
  34.                              [ ] Network [ ] Other: ______
  35. Modem (e.g. Hayes 14.4 FAX):
  36.            Winsock Supplier:
  37.            Operation System: [ ] Windows 3.1
  38.                              [ ] Windows 3.11
  39.                              [ ] Windows for Workgroups
  40.                              [ ] Windows/NT 3.1
  41.                              [ ] Windows/NT 3.5
  42.                              [ ] OS/2 2.x
  43.                              [ ] OS/2 Warp
  44.                              [ ] Windows '95  Version: ________
  45.                              [ ] Other: ______________
  46.  
  47.   Host System or 
  48. Internet Service Provider:
  49.   (e.g. Netcom, Sun/OS etc.)
  50.  
  51.  Other relevant information:
  52.  
  53.  
  54.  
  55.    Bug Report
  56.    __________
  57.  
  58.     Title: 
  59.  
  60.    Priority: [ ] Emergency: GPF or failure causing loss of 
  61.                             data.
  62.  
  63.              [ ] High: Failure of an existing feature that 
  64.                        substantially prevents normal use 
  65.                        of the program.
  66.  
  67.              [ ] Medium: Failure of an existing feature under
  68.                          isolated circumstances that does not 
  69.                          prevent normal use of the program.
  70.                            - OR -
  71.                          Significant design ommision that prevents
  72.                          normal use of the program under certain 
  73.                          circumstances.
  74.  
  75.                          (Note that GPF's or other crashes are 
  76.                          EMERGENCY-priority under any 
  77.                          circumstance).
  78.  
  79.              [ ] Low:  Feedback, feature suggestions, annoying or 
  80.                        difficult-to-use features of the program.
  81.  
  82.    Description:
  83.       (As much as possible, please provide step-by-step instructions
  84.       on how to cause the problem to occur).
  85.  
  86.  
  87.  
  88.  
  89.                             
  90.  
  91.  
  92.