1 <!--#include virtual="/samba/header.html" -->
2 <title>Samba Bug Report HOWTO</title>
3 <!--#include virtual="/samba/header_columns.html" -->
5 <H2 align="center">Bug Reports, Patches & contacting the Samba Team</H2>
7 <BR><p> The Samba Team have recently implemented an
8 improved Bug Tracking System (using <A
9 HREF="https://bugzilla.samba.org/">Bugzilla</A>) to provide
10 better support to the Samba community.
12 <p align=center><em>Please note: all correspondence with the Samba
13 Team can be made through the public Samba mailing lists. Please
14 refer to <a href="http://lists.samba.org/">http://lists.samba.org/
15 </a> for more information on these.</em>
19 <h2>How to use the Bug Tracking System</h2>
21 <p>Sending a bug report to the Samba Team is done by the
23 <a href="https://bugzilla.samba.org">https://bugzilla.samba.org</a>.
24 <em>Note that only legitimate bug reports
25 will be dealt with via the bug tracking system.<br>
26 Any queries for configuration help or general information will
27 be disregarded. Please send such requests
28 to <a href="mailto:samba@lists.samba.org"> samba@lists.samba.org</a>
29 after <a href="https://lists.samba.org/mailman/listinfo/samba">subscribing
30 to the list</a>.</em><br>
33 <p>To make the most of your message and to help
34 everyone get the quickest response please include the information
35 about your operating system, compiler and runtime environment.</p>
37 <h2>How to send patches?</h2>
40 <a href="mailto:samba-technical@lists.samba.org">samba-technical@lists.samba.org</a>
41 Make sure they are in unidiff format and include any
42 necessary documentation changes and take account of cross-platform
43 issues. Half baked patches aren't really much use.</p>
45 <!--#include virtual="/samba/footer.html" -->