Changes between Version 27 and Version 28 of TesterDocumentation

Timestamp:

03/02/16 14:28:52 (8 years ago)

Author:

Samuli Seppänen

Comment:

Clean up bug reporting documentation

TesterDocumentation

@@ -99 +99 @@
 
  * Operating system (e.g. OpenBSD 4.3)
- * Your ''./configure'' command-line
- * The complete output of ''openvpn --version''
+ * The complete output of ''openvpn --version'' or the full filename of the Windows installer you used
+ * Relevant parts of OpenVPN client and/or server logs (when available) at ''verb 5'' verbosity (see [Openvpn23ManPage man-page])
+ * If you built OpenVPN youself: the ''./configure'' command line you used
 
-Whenever possible, also provide logs with appropriate log level (5 or greater) from both the client and server; see ''--verb'' in OpenVPN [http://openvpn.net/index.php/open-source/documentation/manuals.html man-page] for details. Only include the log sections that are relevant to the bug, e.g. with something like this:
+Fill in all the fields in Trac you are able to.
 
-{{{
-$ tail -n 0 -f <openvpn-log-file>
-}}}
-
-Note that if you're testing out a ''new feature'' or trying to ''reproduce a bug'', we'd like to have both ''success'' and ''failure reports''.
+Note that if you've volunteered to test out a ''new feature'' or trying to ''reproduce a bug'', we'd like to have both ''success'' and ''failure reports''.
 
 If the bug you've found is a regression and you want to see it fixed as soon as possible, you can help by doing a ''Git bisect''. This technique is described here:
@@ -115 +112 @@
  * [http://progit.org/book/ch6-5.html Debugging with Git]
 
-If you manage to find the commit that caused the regression, fixing it is ''much'' easier for the developers.
+Bisecting is an advanced technique and you're not expected to do it before filing bug reports.