rsync-web/bug-tracking.html at master · RsyncProject/rsync-web · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>rsync bug-tracking</TITLE>
</HEAD>
<!--#include virtual="header.html" -->

<H2 align="center">rsync bug-tracking</H2>

<p> Please use this checklist combined with the help on the
<a href="issues.html">issues and debugging</a> page before
reporting a bug.  Thanks!

<ul>

<li> If you're not using the latest released version, please upgrade before
reporting a bug.

<li> If you're using the latest released version, consult the
<a href="https://github.com/RsyncProject/rsync/blob/master/NEWS.md">NEWS file from the git repository</a> to see if what
you're seeing has already been handled in the version under development.

<li> It is also helpful to search the bug reports at both the new
<a href="https://github.com/RsyncProject/rsync/issues?q=is%3Aissue">GitHub issues tracker</a> and the old
<a href="https://bugzilla.samba.org/buglist.cgi?product=rsync&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED">bugzilla database</a>
to see if the problem is already known.

<li> See also the <a href="issues.html">issues and debugging</a> page to
help you figure out if what you're seeing is a known bug and perhaps to
help diagnose what is going wrong.

<li> Discuss the bug on the
<a href="https://lists.samba.org/mailman/listinfo/rsync">rsync mailing list</a>
(which is at <tt>rsync@lists.samba.org</tt>) to help you figure out if what
you're seeing is really a bug or a mistake.

<li>There are several patches for features that are under consideration that
can be found in the <a href="https://github.com/RsyncProject/rsync-patches">rsync-patches repo</a>.

<li> If you haven't already done so, please take a couple of minutes to read Simon Tatham's
<a href="https://www.chiark.greenend.org.uk/~sgtatham/bugs.html">advice on how to report bugs</a>.

</ul>

<p> To report a bug or make suggestions, use one of these methods:

<ul>

<li> The mailing list (mentioned above) is a good resource for discussing
bugs and suggesting new features.  It accepts patches (typically as MIME
attachments), but for fixes is often easier to attach a patch to an
appropriate GitHub issue report or use a pull request.  Note that there is
no mandate to use pull requests for patches, as that can be a pretty high
bar of git know-how that not everyone needs to be familiar with.

<li> If you'd like to see a bug-report or feature-request get officially noted,
<a href="https://github.com/RsyncProject/rsync/issues">create an issue on GitHub</a>
(this does require that you have created a GitHub account).  If you want to
stay abreast of what's going on with the issues, make use of the GitHub
subscriptions to pick and choose what kind of notifications you want to
receive (e.g. just a single issue, all issues, all rsync activity, etc.).

<li>For security issues please send email
  to <a href="mailto:rsync.project@gmail.com">rsync.project@gmail.com</a>
  with details of the issue
</ul>

<p> Thanks for helping out!

<!--#include virtual="footer.html" -->