Changes between Version 1 and Version 2 of ReportingBugs


Ignore:
Timestamp:
07/08/08 12:09:52 (10 years ago)
Author:
avel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReportingBugs

    v1 v2  
    22 
    33Since July 2008, Avelsieve is using trac for keeping track (no pun intended) of issues and feature requests. 
     4 
     5 
     6---- 
     7 
     8== Accessing the Bug Tracking System == 
     9 
    410 
    511In order to enter new tickets in the tracker, and to contribute in any way in Avelsieve trac (for instance, update a wiki page or comment on existing tickets), you will need a '''verified email.uoa.gr account'''. 
     
    2935[https://email.uoa.gr/trac/avelsieve/login Login to Avelsieve Trac ] (or use the Login link on the upper right corner) with your email.uoa.gr email/password. 
    3036 
     37 
     38---- 
     39 
     40 
     41== Submitting Bugs == 
     42 
     43=== Step 1 === 
     44 
     45Search existing tickets in case the issue has already been reported. 
     46 
     47 
     48=== Step 2 === 
     49 
     50Edit your configuration file ('''config/config.php''') and set '''AVELSIEVE_DEBUG''' to '''1'''. 
     51 
     52 
     53=== Step 3 === 
     54 
     55Try to recreate the problem. If it has happened due to the generated script being incorrect, then when avelsieve tries to upload the script again, this will generate the error and the whole SIEVE script will appear on the output. 
     56 
     57In your bug report, include: 
     58 
     59* The generated Sieve script, if applicable (copy & paste it from the debug output) 
     60* The error message 
     61 * A description of what you did to trigger it