+<!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>
+<H2 align="center">rsync bug-tracking</H2>
-<p> If you think you have found a bug in rsync we would appreciate
-it if you would check the <a href="issues.html">list of current
-issues</a> and
+<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://download.samba.org/pub/unpacked/rsync/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
<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">search the bugzilla database</a>
to see if the problem is already known.
-<p> Also, please take a couple of minutes to read Simon Tatham's
-<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">advice
+<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://gitweb.samba.org/?p=rsync-patches.git">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> <a href="https://bugzilla.samba.org/enter_bug.cgi?product=rsync">Report
-a bug via bugzilla</a> (this does require that you have created a bugzilla
-account, but that is a very simple process). Set <i>Severity</i> to
-<i>Enhancement</i> if you're making a suggestion.
+<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 bugzilla report.
-<li> Send an email to the
-<a href="http://lists.samba.org/mailman/listinfo/rsync">rsync
-mailing list</a>, which is at <tt>rsync@lists.samba.org</tt>. You
-can send patches to the list too.
+<li> If you'd like to see a bug-report or feature-request get officially noted,
+<a href="https://bugzilla.samba.org/enter_bug.cgi?product=rsync">create a
+report via bugzilla</a> (this does require that you have created a bugzilla
+account, but that is a very simple process). All new items and changes to
+existing items generate email to the mailing list, so the list naturally stays
+up-to-date with what is happening in the bug-tracking database.
</ul>
git.samba.org / rsync-web.git / blobdiff