Changes between Version 13 and Version 14 of BugReporting

Timestamp:

2013-06-20 19:52:34 (11 years ago)

Author:

jeroens

Comment:

--

BugReporting

@@ -1 +1 @@
 = Bug Report =
-We do our very best to deliver you stable and feature-rich software. Yet, issues may bypass our tests; we're a small team and the software can be used in many different ways. This is the section where you can let us now about behaviour of Ecopath versions 5 and 6 that you think is not correct, and where you can submit suggestions for improvement of the software. In this wiki, any user report is referred to as a 'ticket'.
+We do our very best to deliver you stable and feature-rich software. Yet, issues will occasionally not be caught by our tests; we're a small team,  and the software can be used in many different ways for a wide range of purposes. Bug reports are best ways to inform us of unexpected behaviour of the EwE software 6, or to submit suggestions for improvement of the software.
 
 == Pending tickets ==
-You can find all reported tickets listed [http://sources.ecopath.org/trac/Ecopath/report here].
+All tickets opened since the start of the EwE6 project in 2006 can be found [http://sources.ecopath.org/trac/Ecopath/report here].
 
 == Reporting new tickets ==
-Please [http://sources.ecopath.org/trac/Ecopath/search search the list of open tickets] before you [http://sources.ecopath.org/trac/Ecopath/newticket report a new ticket]; people may have already addressed the same issue.
+Please [http://sources.ecopath.org/trac/Ecopath/search search the list of open tickets] before you [http://sources.ecopath.org/trac/Ecopath/newticket report a new ticket]; people may have already addressed the same issue. If you do not have user name and password access to the ticket system you can either report the ticket [mailto:ewedevteam@gmail.com?subject=EwE%20issue%20report by email], or [mailto:ewedevteam@gmail.com?subject=Requesting%20EwE%20bug%20tracker%20account request a bug tracker account].
 
 === Best practices ===
@@ -12 +12 @@
 
  1. A concise but informative title that explains the essence of the problem
+ 1. The version number of EwE that caused the problem
  1. A list of steps explaining how to reproduce the bug
  1. Lastly, a sentence on what was experienced instead of the expected behaviour