1 2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 3 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 4 5 <html xmlns="http://www.w3.org/1999/xhtml"> 6 <head> 7 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> 8 <title>SLF4J Bug reporting</title> 9 <link rel="stylesheet" type="text/css" media="screen" href="css/site.css" /> 10 </head> 11 <body> 12 <script type="text/javascript">prefix=''; 13 </script> 14 15 <script src="templates/header.js" type="text/javascript"></script> 16 <div id="left"> 17 <script src="templates/left.js" type="text/javascript"></script> 18 </div> 19 <div id="content"> 20 21 22 <h1>Before you report a bug</h1> 23 24 <p>The SLF4J community consists of those who use SLF4J and its 25 implementations, help answer questions on discussions lists, 26 contribute documentation and patches, and those who develop and 27 maintain the code for SLF4J and its implementations. Almost all 28 those who assist on a day to day basis resolving bug reports do 29 this for a wide variety of reasons, and almost all of them do this 30 on their own time. 31 </p> 32 33 <p>Many bugs reported end up not being a bug in SLF4J, but are due 34 to misconfiguration, problems caused by installed applications, 35 the operating system, etc. 36 </p> 37 38 <p>Before reporting a bug please make every effort to resolve the 39 problem yourself. <em>Just reporting a bug will not fix it. A good 40 bug report includes a detailed description of the problem and a 41 succinct test case which can reproduce the problem.</em> 42 </p> 43 44 <h3>Review the documentation</h3> 45 46 <p>Review the documentation for the version of component you are 47 using. The problem you are having may already be addressed in the 48 docs. 49 </p> 50 51 <h3>Search the mailing list archives</h3> 52 53 <p>It is very likely you are not the first to run into a problem. 54 Others may have already found a solution. Our various <a 55 href="mailing-lists.html">mailing lists</a> are likely to have 56 discussed this problem before. 57 </p> 58 59 <h3>Search JIRA</h3> 60 61 <p>Please search the bug database to see if the bug you are seeing 62 has already been reported. The bug may have already been fixed 63 and is available in a later version. If someone else has reported 64 the same bug, you could add supporting information to help 65 reproduce and resolve the bug. 66 </p> 67 68 <ul> 69 <li><a 70 href="http://jira.qos.ch/issues/?jql=project%20%3D%20SLF4J">Search for 71 SLF4J bugs</a></li> 72 </ul> 73 74 <h3>Reporting a bug</h3> 75 76 <p>Only after you have exhausted the aforementioned steps, should 77 you file a formal report in JIRA, our bug tracking system. 78 </p> 79 80 <p>Please make sure you provide as much information as 81 possible. Its very hard to fix a bug if the person looking into 82 the problem can't reproduce it. 83 </p> 84 85 <script src="templates/footer.js" type="text/javascript"></script> 86 87 88 </div> 89 </body> 90 </html> 91
