source: public/content/bugreporting.shtml

Last change on this file was 14741, checked in by Mark Evenson, 9 years ago

html: change references from lisp.not.org to abcl.org and common-lisp.net as appropiate.

abcl.org names all permanent ABCL specific resources.

common-lisp.net replaces lisp.not.org as naming for non-ABCL specific
resources.

  • Property svn:keywords set to Id
File size: 2.7 KB
Line 
1<?xml version="1.0"?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
5<head>
6  <title>Bug reporting</title>
7  <link rel="stylesheet" type="text/css" href="style.css"/>
8  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
9</head>
10
11<body>
12 <div class="header">
13   <h1>Bug reporting</h1>
14 </div>
15
16<!--#include virtual="left-menu" -->
17
18<div style="margin-left:auto;margin-right:auto;width:20cm">
19
20
21
22
23
24
25
26  <h2>A quick guide to producing meaningful bug reports for ABCL</h2>
27
28This guide describes how to report bugs in ABCL. When you think you've
29found a bug, send a bug report to the <a href="http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel">mailing list</a>. For the bug report
30to be most useful, try and do the following things:
31
32<ol>
33  <li> 
34    Use a descriptive subject, stating a brief summary of the bug, and
35    mentioning that you're reporting a bug. Don't be fussy about the format
36    of the subject, we don't process the bugs automatically, just try to
37    provide a meaningful description.</li>
38  <li>
39    Add a short program snippet that demonstrates what ABCL does incorrectly,
40    and if necessary, quote any relevant portions in the <a href="http://www.lispworks.com/documentation/HyperSpec/Front/index.htm">Common Lisp standard</a>.
41  </li>
42  <li>
43    Differences between ABCL and other Common Lisp implementations are useful
44    information, if you find that some other Common Lisp implementation works
45    correctly and ABCL has a bug, it helps us in fixing the problem, so
46    try your program snippet on other implementations as well and post
47    the results.
48  </li>
49  <li>
50    Try and answer any questions asked about your bug report.
51  </li>
52  <li>
53    It is very much appreciated if you can actually find what's causing
54    the bug in ABCL codebase and even better still if you can produce
55    a <a href="contributing.shtml">patch</a> that fixes the problem. Don't
56    fret if you can't, though, reports without patches are warmly welcomed, but
57    we highly appreciate patch contibutions.
58  </li>
59</ol>
60
61After all that, sit back, relax and enjoy yourself, the bug should
62get fixed eventually. The maintainers of ABCL are usually rather
63busy, but we will take a look at all bug reports when we have time.
64</div>
65<div style="float:left;width:100%">
66 <hr />
67 <p>Hosted as part of  <a href="http://common-lisp.net/">common-lisp.net</a>.</p>
68
69 <div class="check">
70   <a href="http://validator.w3.org/check/referer">Valid XHTML 1.0 Strict</a>
71 </div>
72<div style="float:right;font-size:10px;font-family:monospace">$Id: bugreporting.shtml 14741 2015-01-05 16:44:38Z mevenson $</div>
73</div>
74
75</body>
76</html>
Note: See TracBrowser for help on using the repository browser.